[jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1642) The <security-domain> tag included in <container-configuration> in the jboss.xml file is ignored

John Gonon (JIRA) jira-events at lists.jboss.org
Wed Dec 17 07:01:54 EST 2008


The <security-domain> tag included in <container-configuration> in the jboss.xml file is ignored
------------------------------------------------------------------------------------------------

                 Key: EJBTHREE-1642
                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1642
             Project: EJB 3.0
          Issue Type: Bug
          Components: Security
    Affects Versions: HEAD
         Environment: Windows XP
JDK 1.6.build10
JBOSS 5.0.0.GA
            Reporter: John Gonon
            Priority: Minor


The <security-domain> tag included in <container-configuration> in the jboss.xml file is ignored.
I have tracked were the problem seems to be (at least as I saw it).

In the class "org.jboss.ejb3.security.bridge.SecurityDomainMetaDataBridge" there are those lines:
         //TODO: How to get the merged meta data? Is the following line correct? 
         if(securityDomain == null)
        	 securityDomain = beanMetaData.getJBossMetaData().getSecurityDomain();

I replaced them with:
            if (securityDomain == null) {
                JBossMetaData metaData = beanMetaData.getJBossMetaData();
                securityDomain = metaData.getContainerConfiguration(beanMetaData.determineConfigurationName())
                        .getSecurityDomain();
                if (securityDomain == null)
                    securityDomain = metaData.getSecurityDomain();
            }

As I understand it, if no "SecurityDomain" annotation is found, then we finish in this class and we do in order:
1. seek for a security domain in the bean's metadata (I guess it is in the EJB declaration)
2. seek for the one in "jboss-app.xml"

I inserted between them some code returning the one comming from the container's configuration

I hope this helps ...

Best regards,
Please keep me informed,
I hope to remove my "modified" jar with an official one soon.

John

-- 
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