aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alasdair Nottingham (JIRA)" <>
Subject [jira] Resolved: (ARIES-431) Add support for "bad" OSGi Web container implementations
Date Thu, 30 Sep 2010 09:46:33 GMT


Alasdair Nottingham resolved ARIES-431.

    Fix Version/s: 0.3
       Resolution: Fixed

> Add support for "bad" OSGi Web container implementations
> --------------------------------------------------------
>                 Key: ARIES-431
>                 URL:
>             Project: Aries
>          Issue Type: Improvement
>          Components: JNDI
>            Reporter: Alasdair Nottingham
>            Assignee: Alasdair Nottingham
>             Fix For: 0.3
> 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.

View raw message