Ganesan,
Thanks for your reply and extended research.
You referred to the below para in sun's documentation
"In a Web-centric design, Web tier components using container services such as the
JDBC API can communicate directly with the enterprise information system resources that hold application data. In this approach, Web tier components are responsible for almost all of the application functionality. They handle dynamic content generation, content presentation, and user requests. They must implement core application functionality, such as order processing and enforcing the application's business rules. Finally, the Web tier components must also manage transactions, such as by using JTA, and connection pooling for data access. Because it must handle so many functions, Web-centric application software can easily become monolithic. As a result, unless special efforts are taken, it does not scale well with increasing software complexity."
When we consider web centric approach do we mean that services such as
- connection pool not available ? (With
tomcat we can have connection pooling within container)
It mentions that the the web centric approach does not scale well when complexity grows. But, for the given question where transaction is not required what approach is better?