Hi Roland,
I looked into this I think this is fixed in trunk or in the 1.1.x branch
with PAXWEB-298
could you verify that this is also a solution for you or if we need to
take a closer look
at it. :)
regards, Achim
Am 03.09.2011 13:06, schrieb Achim Nierbeck:
Hi Roland,
thanx for the bug report,
I will try to see into this during the weekend.
regards, Achim
Am 02.09.2011 20:28, schrieb Roland Brand:
Hi there
I am using Pax Web in Version 1.1.1 with Jetty 7.5.0.RC0.
I registered servlets from several bundles with different
HttpContexts and one
of them is registered for the root path ("/"). The code looks similar
to this:
bundle 1:
httpService.registerServlet("/", servlet1, null, context1);
bundle 2:
httpService.registerServlet("/example", servlet2, null, context2);
A request for "/myFile.html" is correctly handled by context1, but a
subsequent request to "/example" is also handled by context1 (leading
to an
Error 404) instead of context2.
My debugging session lead me to the class
org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection
where
the handle() method calls super.handle(). My request is handled by
the super
class instead of the following code (line 74).
Investigating the source repository I found out that this call to
super.handle() was introduced with the Issue PAXWEB-269. According to
the
Javadoc of the class and my experience, this seems to be a bug.
Could anyone please check this code and verify my thesis?
Thanks a lot
Roland
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
--
--
*Achim Nierbeck*
Apache Karaf<http://karaf.apache.org/> Committer& PMC
OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer&
Project Lead
blog<http://notizblog.nierbeck.de/>
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
