Hi Jean Yes I know the restriction but we have to. Consider millions of records should be processed in a banking system in fiscal year end period and we can't start process one by one. We need a batch processing utility to improve performance and obtain the result in lowest possible time and this is not applicable unless using concurrent jobs.
Jean-Louis MONTEIRO wrote: > > From my understanding, enterprise beans should NOT create/manage thread. > The EJB container is responsible for managing system-related functionality > such as security, threading, resource pooling, and so on. > > http://java.sun.com/blueprints/qanda/ejb_tier/restrictions.html#threads > > So, seems to be dangerous to do that ! > > Regards, > Jean-Louis > > > > is_maximum wrote: >> >> I have a problem when I want to lookup my session beans. >> I have declared @EJB on the session bean in which a POJO class will be >> created using reflection and will be executed in a separate thread. >> > > ----- -- Regards Mohammad Norouzi Help each other to reach the future faster http://pixelshot.wordpress.com Pixelshot Photoblog http://brainable.blogspot.com Brainable Blog -- View this message in context: http://www.nabble.com/problem-in-looking-up-local-interfaces-and-reflection-tp22413263p22555559.html Sent from the OpenEJB User mailing list archive at Nabble.com.
