Add support for "bad" OSGi Web container implementations
--------------------------------------------------------
Key: ARIES-431
URL: https://issues.apache.org/jira/browse/ARIES-431
Project: Aries
Issue Type: Improvement
Components: JNDI
Reporter: Alasdair Nottingham
Assignee: Alasdair Nottingham
I was playing around with the Jetty implementation of the OSGi web container
chapter. It has some interesting behaviours, the most significant is it sets
the java.naming.initial.context system property, but doesn't register it in the
service registry. It relies on the default JDK JNDI behaviour which uses the
thread context classloader to load the initial context factory. Gemini Web has
a similar bug. I can't fix those web container implementations, but since I
want to be able to use these I need a solution. Rather than a bespoke solution
that works for me with Jetty I'll check in a new project which will provide a
bundle to fix these buggy OSGi Web container implementations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
