Yes, we are deploying our OSGi container inside Tomcat (or Jetty, depending on the day). The important distinction may be that we are not loading Shiro as an OSGi bundle. It is a classpath dependency of our webapp itself. When we start Felix (or Equinox), we export Shiro from the jars in the webapp's classpath as a set of system-level bundles--common to the entire OSGi container and available in every classloader.
Best regards, Bryan Turner > From: [email protected] > To: [email protected] > Subject: Re: Cant access subject with Eclipse RAP > Date: Mon, 10 Jan 2011 17:16:37 -0800 > CC: [email protected] > > On Monday, January 10, 2011, Bryan Turner wrote: > > Lothar, have you tried adding Shiro into the seed bundles exported by the > > OSGi container? Those packages are available in all class loaders, and are > > the same instances. That's how we're publishing Shiro in our OSGi > > application (built on Felix, but we've also tested it on Equinox) and it > > appears to work without any issues. > > > > Best regards, > > Bryan Turner > > If I use Shiro in my pure OSGi RCP Eclipse app, I have no such problems. > I only have the problems in the RAP application which uses the equinox server > bridge to run equinox inside the web container (tomcat). > Are you running your OSGi in a web container (tomcat), too? > > The servlet bridge is a bit funky, as one needs to copy the jar files one > wants to access from the web container into the WEB_INF/lib directory, > otherwise the web container won't find them, whereas the wrapped equinox > application has it's bundles in WEB-INF/plugins. Don't ask me why the gods of > equinox choose that particular layout. > > Lothar
