servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt Westerfeld (JIRA)" <>
Subject [jira] Created: (SM-2049) Servicemix Jetty Bundle Missing JAAS Artifacts (jetty-plus/jetty-naming)
Date Tue, 01 Feb 2011 23:27:28 GMT
Servicemix Jetty Bundle Missing JAAS Artifacts (jetty-plus/jetty-naming)

                 Key: SM-2049
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-core
    Affects Versions: 4.0
         Environment: Fuse ESB 4.3
            Reporter: Kurt Westerfeld

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:

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:


View raw message