|
Ivan, I would stick with simple unless you are adding a new feature to an existing EJB-based application. The simplest pooling I have used is Proxool, which took about 1 hour to implement. Tomcat or another servlet container should handle most threading and session needs but you should become familiar with servlet filters, which can be very helpful in setting up your session. I have had good luck with Hibernate and it scales well. A bonus is that I can develop my applications stand-alone on my PC with something like MySql. A drawback is that in some cases (like heavy duty reporting) a persistence layer will add too much overhead. David Morris >>> iva030@xxxxxxxxx 3/8/2004 9:04:32 AM >>> Joe, I am in the infancy stage with this design, so I can go in any direction. Using EJB is the major decision I am still grapling with. I understand what you are saying about using JDO for data access, however, what about all the other system level functionality that an EJB server/container provides... i.e. the connection pooling, thread mgmt, session/state mgmt, etc? I'd rather not code any of that.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.