Ian McCallion wrote:
> EJB's main weakness today is that is is a synchronous model. You'll need
to wait
> for EJB2 (or go with proprietary extensions, which a couple of vendors
have) if
> you want integration with asynchronous messaging.
Would you elaborate a little on this, please?
I can understand that beans seem to be intended to be synchronously
called from some other component. What would an asynchronous model
add to the current synchronous model?
How does JMS fit into this? Are beans prohibited from having message
handler methods? Or is that still considered synchronous?
If I wanted to implement some sort of active agent that lives in the
EJB server, is there any way to do this? In other words, can I create
a thread that remains active in the container?
What is planned for EJB2 that will help asynchronicity (is that a
word? ;-)? Any references appreciated.
TIA for any info,
Paul
===========================================================================
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".
