I am learning EJB3.0. I have written a MDB using @MessageDriven annotation and succeeded too. But, I am little bit confused about the attribute "mappedName". Is this same like jndi name we give with @ActivationConfigProperty in activationConfig attribute.
What exactly "mappedName" would do? Can you guys please explain this?
igor bolsovitch wrote:Just because in glassfish it works ... as expected:
Annotation Type MessageDriven
Optional Element Summary
A product specific name(e.g. global JNDI name of a queue) that this message-driven bean should be mapped to.
You just posted only a part of the javadocs The more important part of the javadocs reads as follows:
...Application servers are not required to support any particular form or type of mapped name, nor the ability to use mapped names. The mapped name is product-dependent and often installation-dependent. No use of a mapped name is portable.
The first (OrderBean) has to send message to the queue orderQueue.
The second (EmailSenderBean) should realize that a new message has come (method onMessage) and should execute a buisiness method (Send an E-mail)
But it doesn't work : It seems that EmailSenderBean does not listen, because when I deploy my application I see this error in jboss:
Is that normal that he logs about the DLQ while in MDB I have :