[
https://issues.apache.org/jira/browse/FELIX-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531033
]
Alin Dreghiciu commented on FELIX-379:
--------------------------------------
Rob,
If you wanna use Jetty 6 you may take a look at pax web. It requires java 5 but
I gues I can make it run also on 1.4. Release 0.2.1 will be out soon.
http://wiki.ops4j.org/confluence/x/AYAz
There is also there Pax Web Extender that allows easy registration of
servlets/resources via a white board model that works with any osgi http
service implementation.
http://wiki.ops4j.org/confluence/x/eYA6
> Registering multiple servlets may hide some
> -------------------------------------------
>
> Key: FELIX-379
> URL: https://issues.apache.org/jira/browse/FELIX-379
> Project: Felix
> Issue Type: Bug
> Components: HTTP Service
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 1.0.0
>
> Attachments: FELIX-379.patch
>
>
> Consider registering a servlet RootServlet for "/" first and then a servlet
> SomeServlet for "/some" with different OSGi HttpContext instances in this
> order with the http.jetty HttpService. This registration works absolutely
> correct and also creates the necessary setup internally. Unfortunately, when
> Jetty now receives a request for "/some", it first calls the RootServlet
> instead of the SomeServlet as would be expected according to the HttpServlet
> Service specification.
> If the servlets are registered SomeServlet first and then RootServlet it
> works perfectly.
> I think it is related to the fact, that the http.jetty bundle registers a
> jetty context for "/" for each different OSGi HttpContext and jetty asks
> these registrations in registration order, which may not be correct according
> to the spec. Probably, there should only be one actual web app registration
> with jetty and the http.jetty bundle should multiplex between the different
> OSGi HttpContext instances and select the correct servlets.
> I am working a possible solution to this right now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
