EJB 3.0 Bean name

Question

Is there a way that we can override the EJB 3.0 Bean name in the deployment descriptor? I know we can provide the name in the Annotation via @MessageDriven(name="bar").
For example, if I have the following Bean,
package com.example;
@MessageDriven
public class Foo implements MessageListener {
When deployed, it always deploys as Foo, even if I have the following in my ejb-jar.xml and weblogic-ejb-jar.xml:
<mesage-driven>
<ejb-name>Bar</ejb-name>
<ejb-class>com.example.Foo</ejb-class>
<destination-type>javax.jms.Topic</destination-type>
<subscription-durablility>Durable</subscription-durablity>
</message-driven>
<mesage-driven>
<ejb-name>Baz<r</ejb-name>
<ejb-class>com.example.Foo</ejb-class>
<destination-type>javax.jms.Queue</destination-type>
</message-driven>
There seems no way I can re-use the Same bean class with EJB 3.0 if I needed to. If there is anyway, the ejb-name can be used please let me know.
Thanks

Answer 1

Hi,
For a JEE5 EJB module, rather than using EJBGen, you can use WLS specific annotations for configuring common settings. If you follow the link below, you can see a list of supported EJB annotations. Disregard the fact that the documentation section title is WebLogic Kodo Annotations. That is incorrect and I've filed a bug for it.
http://edocs.bea.com/wls/docs103/ejb30/annotations.html#wp1438036.
Unfortunately, we don't yet support setting all weblogic-ejb-jar.xml configuration values via annoations so in some cases a weblogic-ejb-jar.xml is still required.
You can hand edit your weblogic-ejb-jar.xml and the example you posted below should work fine.
- Matt