Dimitar Stavrakov wrote: > > > The functionality provided to you by the EJB container is time that you > cannot make up by a generator. Just think about connection pooling,
This can be done without a EJB container. There are a number of free and commercial implementations that do it. > transaction management, etc. You have to be more specific. JDBC does transactions. > When you're using EJBs all these are ready for > you to use, without having to write a single line of code. You can't beat > that with straight JDBC coding. Using all of that functionality, especially the first time for each different container, takes a non-trivial amount of time to configure and tune. There is probably an EJB container that provides easy and clear documentation that makes such chores a breeze. However I haven't seen it nor heard of it. (I spent a week one time trying to get a container set up to do connection pooling with a particular database and driver and I finally had to give up.) That time also counts against the total time for coding any new implementations. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
