[
https://issues.apache.org/jira/browse/FELIX-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14552452#comment-14552452
]
Ferry Huberts commented on FELIX-4888:
--------------------------------------
I have the same problem as David, I followed the thread
{noformat}
Hi all,
I was wondering whether anyone has got the webconsole with the latest
Felix HTTP implementation running yet?
webconsole 4.2.9-SNAPSHOT works perfectly fine with http api/jetty
2.3.2, but doesn't seem to work with 3.0.x-SNAPSHOT of these. It does
resolve, but it does not render properly. Is that simply a TODO or is
there something I need to do to enable this?
Thanks,
David
{noformat}
In the thread you say issue 4888 is for that bug.
I'm using
{noformat}
./org.apache.felix.configadmin/org.apache.felix.configadmin-1.8.2.jar
./org.apache.felix.eventadmin/org.apache.felix.eventadmin-1.4.2.jar
./org.apache.felix.fileinstall/org.apache.felix.fileinstall-3.5.0.jar
./org.apache.felix.framework/org.apache.felix.framework-4.6.1.jar
./org.apache.felix.gogo.command/org.apache.felix.gogo.command-0.14.0.jar
./org.apache.felix.gogo.runtime/org.apache.felix.gogo.runtime-0.16.2.jar
./org.apache.felix.gogo.shell/org.apache.felix.gogo.shell-0.10.0.jar
./org.apache.felix.http.api/org.apache.felix.http.api-2.3.2.jar
./org.apache.felix.http.jetty/org.apache.felix.http.jetty-3.0.2.jar
./org.apache.felix.http.servlet-api/org.apache.felix.http.servlet-api-1.1.0.jar
./org.apache.felix.metatype/org.apache.felix.metatype-1.0.12.jar
./org.apache.felix.scr/org.apache.felix.scr-1.8.2.jar
./org.apache.felix.webconsole/org.apache.felix.webconsole-4.2.8.jar
{noformat}
> ServletHandler's are not sorted by longest matching path
> --------------------------------------------------------
>
> Key: FELIX-4888
> URL: https://issues.apache.org/jira/browse/FELIX-4888
> Project: Felix
> Issue Type: Sub-task
> Components: HTTP Service
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: http.base-3.0.0
>
>
> If more than one servlet handler matches the request, the result is sorted by
> service ranking and not by longest matching path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
