When I deploy my .ear files where I have one EJB reference another one I get deployment errors in 3.2.5 that I don't get in 3.0.8. This happens both in the case when the EJBs are in the same jar (and therefore same .ear) and when they're in a different .ear file.

Did the specification of how to make such a reference change? If so, can anyone tell me how it works now? (And possibly: why did it change?)

The following is more information regarding the error in the case the EJBs are in separate .ear files.

org.jboss.deployment.DeploymentException: Error in jboss.xml for Bean VolatilityManager: expected one ejb-ref-name tag at org.jboss.metadata.ApplicationMetaData.importJbossXml(ApplicationMeta
Data.java:764)

My jboss.xml looks like this:

<enterprise-beans>

<ejb-name>VolatilityManager</ejb-name>
<jndi-name>saen/VolatilityManager</jndi-name>
<ejb-local-ref>
<ejb-link>UnderlyingManager</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<ejb-link>DividendManager</ejb-link>
</ejb-local-ref>


</enterprise-beans>

and ejb-jar.xml like this (if it's relevant to this problem):

<ejb-jar>
<display-name>Volatilities</display-name>
<enterprise-beans>

<resource-ref>
<res-ref-name>jdbc/DefaultDS</res-ref-name>
<jndi-name>java:/DefaultDS</jndi-name>
</resource-ref>


<ejb-name>VolatilityManager</ejb-name>
saen.volatility.common.VolatilityManagerHome
saen.volatility.common.VolatilityManagerEJB
<ejb-class>saen.volatility.server.VolatilityManagerBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>


</enterprise-beans>

<assembly-descriptor>
<security-role>
<role-name>admin</role-name>
</security-role>
<method-permission>
<role-name>admin</role-name>

<ejb-name>VolatilityManager</ejb-name>
<method-name>*</method-name>

</method-permission>
<container-transaction>

<ejb-name>VolatilityManager</ejb-name>
<method-name>*</method-name>

<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>