I just finished reading the CRM section of Ben Forta's CFMX/J2EE book and am curious about using Entity Beans for database access. The book described them as fairly involved to develop and deploy and provided relatively poor performance. One of the issues discussed with the application, albeit fictional, was the slow response time of the Entity EJB's.
My understanding is if you wanted to use an EJB for db access and take advantage of object pooling and distributed deployment you can use a stateless session bean with JDBC code to query the database and return Java objects. That said, you can still use CFQUERY and access J2EE level datasources attached to the app server's connection pools. Can those of you with experience in J2EE describe which of these you've used and the advantages/disadvantages and why you made that choice? Which would you recommend for a CFMX/J2EE application and what other factors should be taken into account? Thanks, Sam ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
