Re: Entity Beans: Stored Procedure. -400 Tables.

[Johan Eltes]

I wouldn't involve an OTM (like an EJB container) in this scenario. It sounds like a batch job that is naturaly implemented as a Java-startable class, invoked by a scheduler. I think you are fighting the EJB spec, if you start your own threads from within the container. /Johan -----Original Message----- From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Ramakrishna Srinivasa Sent: 03 January 2001 12:30 To: [EMAIL PROTECTED] Subject: Entity Beans: Stored Procedure. -400 Tables. hi, I have a requirement wherein I need to replicate the Data of around 400 Tables. This is being accomplished by means of a Stored Procedure this will take some hours. I am calling this Entity Bean from a Session Bean. What I want is that I should come out of the loop. Hence I am planning to start a separeate thread from Session Bean and call the Ent Bean. As it is the Session bean will be free and I will get the response back to the point from where I called SB. Is it advisable to do like this?? A new Thread from a SB? Transaction is not imp to me here. Any ideas/suggestion will be highly appreciated. Thanks, Ramki. =========================================================================== 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". =========================================================================== 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".