> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of François Exertier
> Why is the ejb-name tag optional for a message driven bean ?
MessageDriven Beans are anonymous JMS Listeners, they are not bound in the JNDI
tree nor can they be referenced directly by other beans. Hence, they do not need
any name.
The only way you can contact a MessageDriven Bean is by sending a message on the
Destination it is listening to.
> How can we define the transactional attribute of the onMessage method
> in the container-transaction element if the message driven bean have
> no ejb-name ?
Good point. A loophole in the specification. If you don't specify the ejb-name,
your MessageDriven Bean will use the default transaction attribute (NOT_SUPPORTED
for WebLogic).
> (Notice that the ejb-name is not given as optional in the comment
> describing the message-driven element).
Once again, good catch. I will forward these remarks to the EJB 2.0 expert group.
--
Cedric
(former Bull employee ;-))
===========================================================================
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".
