Followup question on this, I'm kind of new to EJB and WebLogic. We want to
spawn off separate execution of our tasks so that we can return control to
the caller immediately. We shouldn't spawn our own threads in our beans, so
what else can we do?
Let's assume that we can't use JMS. WebLogic has the concept of a startup
class - a regular java class (non-bean) that is started up by the server.
What if we create a startup class that can accept reuqests, spawn a thread,
and return. In this thread, we would class the beans that we are needed to
perform the tasks. Thus the clients don't have to wait for the app to fully
process (our objective), tasks go on in parallel, and we haven't violated
the EJB threading policy.
Does this make sense? Is there a better approach?
Thanks, Joe
===========================================================================
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".
