You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2011/05/18 12:25:47 UTC
[jira] [Assigned] (SMX4-823) Servicemix Jetty Bundle Missing JAAS
Artifacts (jetty-plus/jetty-naming)
[ https://issues.apache.org/jira/browse/SMX4-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned SMX4-823:
-----------------------------------------
Assignee: Jean-Baptiste Onofré
> Servicemix Jetty Bundle Missing JAAS Artifacts (jetty-plus/jetty-naming)
> ------------------------------------------------------------------------
>
> Key: SMX4-823
> URL: https://issues.apache.org/jira/browse/SMX4-823
> Project: ServiceMix 4
> Issue Type: Bug
> Components: Bundles
> Environment: Fuse ESB 4.3
> Reporter: Kurt Westerfeld
> Assignee: Jean-Baptiste Onofré
>
> The jetty bundle provided by Servicemix is very difficult to get working for applications which need to authenticate and authorize to the JAAS infrastructure provided by Servicemix. I had to:
> - install jetty-naming and jetty-plus
> install -s mvn:org.mortbay.jetty/jetty-naming/6.1.22
> install -s mvn:org.mortbay.jetty/jetty-plus/6.1.22
> - build a fragment bundle that includes that specifies "Fragment-Host: org.apache.servicemix.bundles.jetty-bundle" to and specifies package imports for the following two packages:
> org.mortbay.jetty.plus.jaas
> org.apache.karaf.jaas.modules
> The problem is, resolving this fragment bundle is hard to do, and requires a JVM restart. The reason is a circular dependency between jetty-plus and jetty proper, where jetty-plus includes references to org.mortbay.jetty.*.
> It would be a lot better to at least include jetty-naming and jetty-plus in the jetty bundle, at the very least. And because this jetty bundle would commonly be tied to the JAAS infrastructure of SMX itself, please include a reference to the "org.apache.karaf.jaas.modules" package. I would understand if you did not do that last bit but the former would at least allow a fragment to be installed that references "org.apache.karaf.jaas.modules" and not require a VM restart.
> BTW, to get my fragment bundle I have to:
> osgi:install <myfragment>
> osgi:resolve <myfragment id>
> osgi:update <jetty bundle id>
> And then restart. After restart, the fragment bundle resolves. If I do not do an osgi:update on the jetty bundle, it never resolves.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira