[
http://issues.ops4j.org/browse/PAXWEB-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672#action_13672
]
Guillaume Nodet commented on PAXWEB-221:
----------------------------------------
That's a JAAS problem imho. In Karaf, we recently enhanced that to not tie the
applications to the specific jaas classes.
See
http://karaf.apache.org/manual/2.1.99-SNAPSHOT/developers-guide/security-framework.html#Rolediscoverypolicies
I wonder if that's a better way to solve the problem.
> Dynamic adaption of Manifest
> ----------------------------
>
> Key: PAXWEB-221
> URL: http://issues.ops4j.org/browse/PAXWEB-221
> Project: Pax Web
> Issue Type: Improvement
> Affects Versions: 0.8.1
> Environment: Apache Karaf, Jetty7
> Reporter: Achim Nierbeck
> Assignee: Alin Dreghiciu
>
> Currently if a webapp is deployed in a pax-web container with jetty 7 and
> JAAS Security Enabled, the Application is not able to acces the JAASRole.
> The following exception is logged.
> java.lang.RuntimeException: java.lang.ClassNotFoundException:
> org.eclipse.jetty.plus.jaas.JAASRole not found
> To fix this I would recomend to adapt the Manifest of the Webapplication
> while deploying to dynamical import classes org.eclipse.jetty.*
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
