Shiro itself works fine with OSGi, I didn't mean to imply anything else.
I'm not sure whether or not Apache Shiro includes any OSGi regression tests, but the aim of Pax Shiro is to test all of its own extensions both on Java EE and on OSGi, and of course these regression tests will implicitly also test the underlying Apache Shiro core bundles.
One of the problems I ran into when testing pax-shiro-faces on Equinox is that JSF taglibs do not seem to work well in OSGi in general.
But this is not related to Shiro, you'll see the same kind of issue when trying to use PrimeFaces or any other JSF library which is not embedded in your WAB but provisioned as a separate bundle.
The problem is that META-INF/* config resources from other bundles are not accessible via the WAB bundle classloader by default.
This is addressed by a fragment customizing the Jetty boot bundle. Hope that makes things clearer. Best regards, Harald Am 30.08.2013 19:08, schrieb Chris Geer:
Harald, I was just looking through the site and had a question for you. When you say you extended Shiro to support OSGI, what exactly do you mean? Do you mean you've enabled JSF support for Shiro in OSGI? Or did you do additional work to support Shiro in OSGI generically? We currently use Shiro in our OSGI container today (Apache CXF endpoints) but I'm always looking for better approaches. Would your project be applicable, or is it only really applicable to JSF projects? Thanks, Chris
