Thanks,
I had
==> logs/catalina.out <==
element "security-constraint" occurs more than once. (parent class:
org.apache.cocoon.portal.pluto.om.WebApplicationDefinitionImpl)
location: /web-app/security-constraint{file:
file:/opt/apache-tomcat-5.5.12/webapps/cocoon/WEB-INF/web.xml; line:
627; column: 23}
but true this seems to be an issue with some class in my framework,
maybe not tomcat
When i add some security-role directive in web.xml, seems it doesn't
happen ...
Phil
Mark Thomas wrote:
philguillard wrote:
Hi,
I'd like to set 2 different security contraints : /admin would be
accessible with admin roles and the rest of my application with user
roles. Only one security-constraint directive is allowed
This is not correct. Multiple security constraints are allowed.
How can i manage that ?
Just define the two constraints as per you original post.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]