Details
Major Description
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.