On Tue, Oct 6, 2009 at 10:39 PM, Edelson, Justin < [email protected]> wrote:
> Sten Roger Sandvik wrote: > > The example should be clearer. It's actually set inside the > ProvisionActivator. First statement inside start(..) method. > > servletContext.setAttribute(BundleContext.class.getName(), context); > > Ugh. Not sure how I missed that. Thanks for pointing it out. > > While this is a great addition to Felix, it still feels incomplete in > that I need to write this glue code. For some reason, I was under the > impression that the Felix devs weren't interested in providing a > standard solution to this problem, but perhaps I'm mistaken. Obviously, > people can roll their own solution, but I would like to see something > come "out of the box." There's enough code already in Sling that could > be rolled into Felix to provide this (for example, looking for bundles > in /WEB-INF/resources/bundles/[start level]). > Yes, would very like to get rid of this glue code, but when running inside a WAR you still need some sort of mechanism for starting the container. Perhaps Karaf has a solution for this or maybe there is some need in "core" Felix? The servlet proxy that comes with the servlet brige needs a way to get hold of a bundlecontext so it can track the actual dispatcherservlet that is registered inside OSGi framework. If this is something worth discussing, let me know. Alternatively, I can > just submit a JIRA issue and/or start working on some patches, but I > personally would like to see some consensus on what the desirable > default behavior is. > > Incidentally, the bridge seems to work fine with Servlet 2.4. > > Great. Maybe it's wise to downgrade the servlet api dependencies for http servlet implementation to 2.3 and not 2.5. Will look into this. > Justin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
