I just checked out the answer from Felix in Sling list and his solution sounds reasonable. So, from Sling point of view the solution is resolved whatever the outcome will be related to this.
On Mon, Nov 17, 2008 at 9:15 PM, Mark Derricutt <[EMAIL PROTECTED]> wrote: > I feel like I've opened a big messy can of worms here :( As you say, > hopefully some authoritative answer can be found soon. > > On Mon, Nov 17, 2008 at 9:54 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: >> >> IIRC, the real problem is the OSGi spec (based on Servlet spec 2.1) is >> defining a resolution different from what Jetty does (which I assume >> is Servlet 2.5 spec). Pax Web needs to follow the OSGi spec, even >> though most other Http Service implementations don't at the moment. >> And that in turn creates a problem. Hopefully you will get a >> authorative answer from the CPEG soon. >> > > -- > "It is easier to optimize correct code than to correct optimized code." -- > Bill Harlan > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > > -- Alin Dreghiciu http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. http://malaysia.jayway.net - New Energy for Projects - Great People working on Great Projects at Great Places _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
