I have a Java class that provides various data-retrieval methods (non-transactional). A design decision was made to publish it is a local stateless session EJB in our web app. As I am doing so, I can't help asking myself "why the heck is this being made an EJB?".
Since we have the benefit of connection pooling outside of EJB, and their are no transactions or remote clients, the only possible benefit I can see is that the container would probably pool instances of the bean, and this could be useful at high volume times. Am I missing something else? Does this alone justify making it an EJB? We will deploy to a cluster, but that shouldn't impact this decision, right? Thanks, Mike __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ =========================================================================== 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".
