Details
-
Bug
-
Resolution: Done
-
Major
-
1.0.1.GA, 1.0.1.SP1, jboss-metadata-ejb-2.0.0-alpha-2
-
None
Description
The jboss xsd allows for the jndi-binding-policy to be configured outside of the enterprise-beans section. This jndi-binding-policy should then be applied to all beans in the enterprise-beans section. However, this doesn't happen. The following jboss.xml:
<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: jboss.xml 68870 2008-01-11 09:47:56Z wolfc $ -->
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:jee="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd"
version="5.0">
<jndi-binding-policy>org.jboss.metadata.ejb.test.jndibindingpolicy.DummyPolicy</jndi-binding-policy>
<enterprise-beans>
<session>
<ejb-name>DummyBean</ejb-name>
</session>
</enterprise-beans>
</jboss>
when converted to metadata return null jndi-binding-policy for the DummyBean.
P.S: Note that the jndi-binding-policy probably makes more sense in assembly-descriptor section (as Carlo pointed out on IRC today) of the jboss.xml. So i guess, this might be the time to move it to assembly-descriptor section?