stbischof commented on PR #314: URL: https://github.com/apache/felix-dev/pull/314#issuecomment-2094638951
What you are doing is a absolute valid way. Some OSGi Implementations do embedded the osgi api. And if they embedded it. They should Export it. What i am try to say is, that users of the light bundle at the moment do not get the classes of o.o.servlet from the felix jetty light bundle. If my bundles uses the ServletContextHelper, the bundle has a import header in the manifest that describes that. When my bundle starts it will only start if there is an other bundle that Exports the same package. At the moment felix jetty light is bot the bundle that exports this. You are changing the default behavier. I would like to have it the way around. No export. And no embedded class. In times where developers just used the osgi.cmpn bundle in the setup it may was a good idea to ship also the api with an impl. But now the best practice is to use the api bundle. Long Story short. Maybe @cziegeler could say what the designed behavier here is. ... I hope that this fix in which way ever... solves the issue, the webconsole has when it tries to run with the light bundle. There the ServletContextHelper does not work. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@felix.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
