You are correct that EJB 1.1 does not specify how to do this. This will
be specified fully in EJB 2.0.
In the interim, one way to handle this (as you suggested) is to have an
EJB provide a remote version of onMessage and provide a JMS daemon that
delivers messages via EJB calls. When direct support for JMS is added
the daemon can be eliminated and the message can be delivered via a
special form of message enabled EJBObject.
Robert Patrick wrote:
>
> Mark,
>
> I may be completely missing something here but as it stands today, I don't
> think that the bean instance itself can "be a JMS client" and receive
> messages directly from JMS (i.e., bypassing the EJB Object) and I don't
> know of any way to "make the EJB Object" the JMS client. To have JMS "send
> messages to a bean", I think that you would need some "intermediate object"
> to act as the JMS client and invoke the method on the bean (through the EJB
> Object). If there is a better way, please enlighten me!
>
> Hopefully, Sun will eventually work this out in a future version of the
> specification so that we can eliminate the need for the intermediate object
> (unless you already have a way to do this)...
>
> Thanks,
> Robert
>
===========================================================================
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".
