Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Fri, 17 Jun 2011 21:37:47 +0000 (UTC)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: 
 <1323212469.16593.1308346667361.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (GERONIMO-6015) JACC PolicyContextID conflicts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

JACC PolicyContextID conflicts
------------------------------

                 Key: GERONIMO-6015
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6015
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: security
    Affects Versions: 3.0
            Reporter: David Jencks
            Assignee: Shawn Jiang
             Fix For: 3.0


cf rev 1136332.

There's some kind of PolicyContextId collision, I think between a war module and an ejb embedded inside.  The patch referred to tries to fix this by keeping 2 policy configurations and changing the name of the ejb one. I think its only half complete though because I don't see that the modified PolicyContextID is actually used by the ejb module at runtime. Instead I think we can just add all the security configuration together for all the modules with the same name.  However since I don't know for sure what is causing the original problem I don't know how well this will work.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira