deployment descriptor value overrides the annotation value

[Amit Suresh Pawar]

Hi,
In case of EJB3.0 -> Features ->
You are no longer required to create the EJB deployment descriptor files (such as
ejb-jar.xml). You can now use metadata annotations in the bean file itself to configure
metadata. You are still allowed, however, to use XML deployment descriptors if you want; in the case of conflicts, the deployment descriptor value overrides the annotation value.


I want to know the meanings of the sentence "the deployment descriptor value overrides the annotation value".
Because DD reads ejb-jar.xml at startup.........

Thank You.............
[/LIST]

[Ralph Jaus]

"Deployment descriptor value overrides annotation value" means that the deployment descriptor's values determines the applications configuration at runtime; the overriden annotation value is ignored.

Take the following example:

@Stateless(name="TestBean") 
public class TestBean implements TestInterface
{ 
 ...
 
 @TransactionAttribute(TransactionAttributeType.SUPPORTS) 
 public void doSomething(){ ... }
 
}

If you specify in the deployment descriptor

<ejb-jar>
  <enterprise-beans>
    <session>
      <ejb-name>MyTestBean</ejb-name>
      <ejb-class>test.server.compile.TestBean</ejb-class> 
    </session>
  </enterprise-beans>
  <assembly-descriptor> 
    <container-transaction>
      <method>
        <ejb-name>MyTestBean</ejb-name> 
        <method-name>doSomething</method-name>
      </method> 
      <trans-attribute>Required</trans-attribute>
    </container-transaction> 
  </assembly-descriptor> 
</ejb-jar>     

Then the assignments from the deployment descriptor apply. That means the name of the bean is "MyTestBean", not "TestBean" and the transaction attribute of doSomething is "Required" and not "SUPPORTS".
[ December 22, 2008: Message edited by: Ralph Jaus ]

[Christophe Verré]

Please do not duplicate threads. I've removed the other one.