Laird Nelson wrote:
> 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?
>
Maybe I missed something, but IIRC, EJBs can not use threads because it's the
container's task to create and handle them (and your thread handling code could
"interfere" with the container's). JMS will be implemented by the container, which
is allowed to use threads. So your bean can use JMS.
Another solution would be to make JMS out-of-process.
Regards.
JB.
>
> 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".
--
Jean-Baptiste Nizet
[EMAIL PROTECTED]
R&D Engineer, S1 Belgium
Excelsiorlaan 87
B-1930 Zaventem
+32 2 714 45 42
===========================================================================
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".
