Another reason for using session beans is that they allow you to define their security and transaction requirements of the session beans seperately from the configuration of the message driven beans.
Depending on the amount of work your static methods are going to be performing this may or may not be something you need to consider. If your application code is split up into different beans, with the correct use of ejb references you can change which beans are used by just changing the deployment descriptors without needing to recompile your code. If you have made calls to static methods your only option is to recompile the code. Finally is you are going to use 'memory saved' as an argument for a design decision I think you should make sure that it is quantified. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869874#3869874 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869874 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
