I think I said that on this list 10 times or more.
JMS is a resource manager. JMS is allows to spawn threads. JMS is
integrated with the EJB container through some black magic (called a
transaction monitor). JMS is running in the same Java policy as the EJB
server, not the policy of your EJB beans, thus, is allowed to do
Thread.start() and Thread.stop().
A bean can use JMS just like a bean can use other EJB resources that
mess up with threads (e.g. calling up another bean).
arkin
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?
>
> 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".
===========================================================================
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".
