Andrzej Jan Taramina wrote:
> Rickard wrote:
>
> > Further, there is nothing that prevents Enterprise Beans to be producers
> > of JMS messages, or at least you should not consider the EJB threading
> > restrictions to be the cause, again as has been discussed extensively
> > during the past weeks.
>
> Actually I do not believe you are correct in this.....to be a JMS
> Message producer you need to have an open JMS Session. Session's
> implement Runnable and usually start a separate thread for their JMS
> operations when you create one. This means that an EJB cannot
> create a JMS Session...and without one you cannot do any message
> production.
In theory you may be right but in practice it is not the case. I built a
prototype workflow system using Persistence Software's PowerTier EJB server and
IBM's implementation of JMS on top of MQSeries.
> Just like with message consumers, I belive you would have to build
> external proxies for both message sending and production because of
> this. Not worth the effort since the next EJB spec will integrate JMS
> functionality and allow EJBeans to be both message producers and
> consumers. I believe the current thinking on the integration is that the
> container would supply the "proxies" to the core JMS functionality on
> behalf of the beans, so the restriction on use of threads in EJBeans will
> not be restricted.
>
> Sometimes it is just easier to go with pure JMS....and leave the EJB
> model behind.
>
> Andrzej Jan Taramina
> Chaeron Consulting Corporation
>
> Chaeron: - http://www.chaeron.com
--
Perry Hoekstra - [EMAIL PROTECTED]
-------------------------------------------------
All that is Microsoft does not glitter,
Not all those who wander are lost;
The old AT&T Unix that is strong does not wither,
Deep roots are not reached by frost.
>From the ashes of Spec1170 a fire shall be woken,
A light from the shadows shall spring;
Renewed shall be the Unix OS that was broken,
Linux shall be king.
===========================================================================
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".
