I would suggest not to use threading instead use JMS to pass asynchronous
messages which start processing.
----- Original Message -----
From: Ramakrishna Srinivasa
To: [EMAIL PROTECTED]
Sent: Wednesday, January 03, 2001 4:59 PM
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".
- Entity Beans: Stored Procedure. -400 Tables. Ramakrishna Srinivasa
- Re: Entity Beans: Stored Procedure. -400 Tables... Johan Eltes
- Re: Entity Beans: Stored Procedure. -400 Tables... Rohit Parik
- Re: Entity Beans: Stored Procedure. -400 Tables... Anil Kumar Fanda
- Re: Entity Beans: Stored Procedure. -400 Tables... Arthur C�sar Oreana
- Re: Entity Beans: Stored Procedure. -400 Tables... akula sridhar
