Evan Ireland wrote:
> In virtually every case where we have had customer requests for a thread API
> that is compatible with our server, we have determined that a messaging
> solution (such as JMS) would meet the stated customer requirements.
But try this on for size:
1. EJBs must not manage threads.
1a. Corollary: classes that are not EJBs but that are called by EJBs
must not manage threads.
2. Hypothesis: All asynchronous messaging systems manage threads to
achieve decent performance, even on publishing operations.
3. JMS implementations are not themselves EJBs.
4. (3) + (2) = JMS may not be called by EJBs.
How is a bean supposed to publish a message using a JMS implementation?
Cheers,
Laird
===========================================================================
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".
