The idea of "using always EJB for everything" is wrong.
The scenario you have described may be perfect for implementing remote
object with CORBA (or RMI, of course :-).
You can store your data in a different execution thread (backgroung work),
and so on.
Maybe I don't undesrtand your needs, but my arguments are valid for many
other situations. EJB is not the "panacea" for everything, IMHO.
Regards,
Jesus
===========================================================================
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".
