Hi!
Ashwin Dinakar wrote:
> Thanks to those who informed me that an Enterprise Bean cannot be a JMS
>Consumer. In order to completely eliminate JMS from our design can an Enterprise Java
>Bean at least be a JMS 'producer' ? Or is that ruled out as well because of the EJB
>threading restrictions.
Whoa, slow down a minute. It is correct that currently a Enterprise Bean
cannot be a direct JMS consumer, but there is nothing that prevents you
to do this through a proxy (as discussed and explained in earlier
posts). The only problems are related to the setting up of the proxy
connections, which are not yet defined.
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. See my post on EJB and its relation to the
security API for example
(http://archives.java.sun.com/cgi-bin/wa?A2=ind9911&L=ejb-interest&P=R45924).
Is there anything about this matter that you feel to be unclear, and if
so, what?
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
