Hi all, I have some doubts regarding the proper usage of stateless session beans. My application has a 'session facade' for receiving all external requests. After receiving requests, the facade interacts with 3 other state less session beans(individual components - each having a distinct functionality) to service the requests. And, each of the individual session bean components can interact with one or more entity bean for DB access/updates.
That was my application design - untill I got this doubt: Why should I use stateless session beans for the individual components ? why can't they be plain java classes that access the entity beans(just like the session beans where accessing before) By this I can avoid a JNDI lookup - each time I want to access the component. I'am not sure of the negative effects this may have - related to transactions/scalability..,,. So, I would be happy - if some one can contribute their opinion in this regard. Thanks in advance, Baskar View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867726#3867726 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867726 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
