[jboss-jira] [JBoss JIRA] Commented: (JBMETA-232) jndi-binding-policy configured at top level in jboss.xml does not get applied to the beans configured in that file

jaikiran pai (JIRA) jira-events at lists.jboss.org
Wed Dec 16 13:28:31 EST 2009


    [ https://jira.jboss.org/jira/browse/JBMETA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12500387#action_12500387 ] 

jaikiran pai commented on JBMETA-232:
-------------------------------------

org.jboss.metadata.process.processor.ejb.jboss.JNDIBindingPolicyProcessor has been added. The JNDIBindingPolicyProcessor is responsible for:

/**
 * JNDIBindingPolicyProcessor
 * 
 * A {@link JBossMetaDataProcessor} which ensures that if a bean does not set the 
 * jndi-binding-policy explicitly and if a jndi-binding-policy is set at the deployment level
 * (through top-level in jboss.xml), then that deployment level jndi-binding-policy gets applied to
 * the bean. 
 * 
 */
public class JNDIBindingPolicyProcessor implements JBossMetaDataProcessor<JBossMetaData>

> jndi-binding-policy configured at top level in jboss.xml does not get applied to the beans configured in that file
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMETA-232
>                 URL: https://jira.jboss.org/jira/browse/JBMETA-232
>             Project: JBoss Metadata
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: ejb
>    Affects Versions: 1.0.1.GA, 1.0.1.SP1, jboss-metadata-ejb-2.0.0-alpha-2
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>
> 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? 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list