Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <28814245.1190901770948.JavaMail.jira@brutus>
Date: Thu, 27 Sep 2007 07:02:50 -0700 (PDT)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-379) Registering multiple servlets may
 hide some
In-Reply-To: <32515633.1190789510546.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530730 ] 

Richard S. Hall commented on FELIX-379:
---------------------------------------

Rob Walker has done most of the hacking on this, so perhaps he might have the most valuable input on whether the patch makes sense. However, I am sure you can go ahead and apply it because if it causes issues we can always fix it or rollback.

> 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
>         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.