Dave Van Even

Thanks I got convinced enough now to go that way

Hi;
I don't know exactly where to ask this question (there are so many forums here) but I know some of you guys here can give some insight.
Simple question: If you use an ORM tool would you
a) use it in your domain model (business logic)
b) use it in DAO's that your domain model uses

It looks interesting to really seperate the ORM stuff into DAO's but somehow it's strange
opinions ?
Thank you

howdy
In ASP.NET you can drag some HTML control on a page, double click it and put in some code. I kind of like that idea...
I was kind of wondering wether there is a simular event driven way of dealing with HTML controls in java ?
I've done all my best to make our company switch to J2EE (as this is what I know and what I like best) but they fell for .NET's easyness and Visual Studio.NET (which is a great editor btw)

Why the heck isn't there a single decent editor to help us out with STRUTS ? Where are JavaServer Faces ? What ARE JavaServer Faces ? When is the spec. finally ready ?
Where are some great tag libs to quickly develop websites and seperate code from HTML ? Where are some great taglibs that can be used by tools (like VS.NET)
Dave

hi,
I've been wondering what the best way is to develop EJB's...
- Who writes them from scratch (or uses templates) and maintains the XML manually ?
- Who uses editors with code generation ?
- Who uses XDoclet ?
- Are their any other ways to do it ?
What kind of development tools are their out there to make developping EJB's butt easy ? What are you using ?

I'm trying to convince my project manager to use J2EE instead of MS's .NET but I'm having a hard time convincing him

Why should we go with J2EE ? (the knowledge is here)

Dave

THanks That really made a difference to me

Dave Van Even

Here's an article ( http://www.theserverside.com/resources/article.jsp?l=MonsonHaefel-Column1 ) about the first public draft of the Enterprise JavaBeans 2.1 specification and look what we've got there
Timer Service
--------------------------
The Time Service is a scheduling system that is built into the EJB container. A stateless session or entity bean can register itself with the Timer Service, and request notification at a particular point in time or when a specified period of time has elapsed.
The Timer Service uses a fairly simple programming model. The stateless or entity bean must implement the TimedObject interface.
public interface javax.ejb.TimedObject { public void ejbTimeout(Timer timer); }
When the bean's timer goes off, the container will call its ejbTimeout() method. You can put any kind of business logic you like in ejbTimeout(). For example, an entity bean that represents an invoice might have a timer that activates after 45 days. When the timer goes off, the container calls the ejbTimeout() method. The Invoice entity bean might then send a JMS message to alert an accounts-receivable application that payment is overdue, or send the customer an e-mail requesting payment.
Dunno how long it will take till we can actually use this ? Anyone ?

Dave Van Even

Thanks
Really appreciated it cuz I need some documentation for my manager as it's likely we'll move to J2EE (and all that comes with it)

Dave

Originally posted by Sowmya BC:

This depends on the Application Server that you are using. Most application servers do what is called as 'lazy loading'. When a finder method returns say 100 records, 100 Component Interfaces are created. Its only when you call a method on the bean that a bean instance is created.

Correct me if I'm wrong but aren't BEAN INSTANCES managed by the container and usually put in a pool ?
I understood that when you call a method on a component interface the container activates a pre-loaded bean from the pool (transfers it from unused to used) and loads the data into it. Only after this process the BEAN INSTANCE receives the method call priorly invoked on the component interface.

So 100 component interfaces would be created but these could use for example the maxiumum of 20 BEANS from the pool as they are activated and passivated as nescesary.

Dave

hehe you too !!
(in training too )

thanks you didn't confuse me at all
so basically it comes down to the fact you don't have control over the 'version' of the DTO's at the client side so you force him to get DTO's from a factory so the EJB developer has control over it
Neat

still don't know

How should the beans be packaged ? In one JAR or in multiple jars ?
I've seen people put Entity beans in one and Session in another ... Is this for a reason ?

What is best ?

Hi,
does anybody know a tutorial on XDoclet ? Their documentation site isn't very helpfull for someone new to XDoclet
thanks

Hi,
I don't understand the need for a Data Transfer Object Factory (as explained in 'EJB Design Patterns: Advanced Patterns, Processes, and Idioms by Floyd Marinescu')
Why would you need a DTO Factory ?

Thanks