This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
My application is EJB-centric, but some methods do not require any transaction or security. They're just catalog search methods. I was thinking of accessing the database directly from the web tier. From the web action I would call my DAO. Would this cause any problem? I know I'd need to make sure that both, my web server and my application server, have access to the database. Can you think of any other issue that might arise from this design?
I'd try to keep the architecture clean and consistent and avoid db access from outside the EJB container.
You can make a session bean that runs under bean managed transactions and just never start any transactions. I worked with a vendor framework that deployed the same session bean twice, once as CMT and once as BMT.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Joined: Sep 03, 2004
If I document that my CatalogSearchDAO accesses the DB from the web container, does that still make my architecture unclean and inconsistent?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com