[
https://issues.apache.org/jira/browse/FELIX-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010979#comment-14010979
]
Carsten Ziegeler commented on FELIX-1651:
-----------------------------------------
While RFC-189 will support regexp for filters, it won't support it for
servlets. The main reason is ordering or answering the question which servlets
should service the request if more than one matches. With the patterns from the
servlet api, this can be easily answered as simply the longest matching pattern
wins. With regexp you loose this functionality and things like "the longest
regexp pattern wins" don't make that much sense. For filters this is a
different thing, as all matching filters are invoked.
> Support * in servlet registrations
> ----------------------------------
>
> Key: FELIX-1651
> URL: https://issues.apache.org/jira/browse/FELIX-1651
> Project: Felix
> Issue Type: Sub-task
> Components: HTTP Service
> Affects Versions: http-2.0.2
> Reporter: Mirko Tschäni
>
> At the moment it is only possible to register servlets with aliases like / or
> /some/path. Registering servlets with a wildcard alias (i.e. *.jpg or *.jsp)
> is supported yet.
> I think it would make sense to support wildcards in servlet mappings.
> I have also noticed, that filter mappings do support regular expressions in
> aliases, it might make sense to support regular expressions in servlet
> mappings as well (all though it is a little bit confusing to see that /test/*
> does not match /test/hello.txt in filter mappings, but i still prefer using
> regular expressions over the limited wildcard support in standard jee servlet
> mappings).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
