[jira] [Commented] (FELIX-1651) Support * in servlet registrations
[ https://issues.apache.org/jira/browse/FELIX-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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)
[jira] [Resolved] (FELIX-4524) Substituted exports may cause IndexOutOfBoundsException
[ https://issues.apache.org/jira/browse/FELIX-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard S. Hall resolved FELIX-4524. Resolution: Fixed Fix Version/s: resolver-1.2.0 Assignee: Richard S. Hall I've applied the patch, please close if satisfied. Thanks! Substituted exports may cause IndexOutOfBoundsException --- Key: FELIX-4524 URL: https://issues.apache.org/jira/browse/FELIX-4524 Project: Felix Issue Type: Bug Components: Resolver Reporter: Thomas Watson Assignee: Richard S. Hall Fix For: resolver-1.2.0 Attachments: org.apache.felix.resolver.patch In some cases substituted exports can cause IndexOutOfBoundsException. This can happen if you have a substituted export for which the exported capability is the only capability that can satisfy one or more other requirements. For example: BSN: A Import-Package; substituted; version=[1.0,1.1) BSN: B Export-Package: substituted; version=1.0 Import-Package: substituted; version=1.0 BSN: C Export-Package: substituted; version=1.1 Import-Package: substituted; version=1.1 Resolving A as a root resource will cause something like the following exception: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:635) at java.util.ArrayList.get(ArrayList.java:411) at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:692) at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:251) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (FELIX-4060) Implement HTTP Service Update (RFC-189)
[ https://issues.apache.org/jira/browse/FELIX-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011127#comment-14011127 ] Carsten Ziegeler commented on FELIX-4060: - I've created a branch from the current head at https://svn.apache.org/repos/asf/felix/sandbox/http-rfc189/ Implement HTTP Service Update (RFC-189) --- Key: FELIX-4060 URL: https://issues.apache.org/jira/browse/FELIX-4060 Project: Felix Issue Type: New Feature Components: HTTP Service Reporter: Carsten Ziegeler The OSGi early draft 2013-03 contains a version of RFC 189, the HTTP service update. This issue is for keeping track of the changes and their implementations -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (FELIX-4060) Implement HTTP Service Update (RFC-189)
[ https://issues.apache.org/jira/browse/FELIX-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011127#comment-14011127 ] Carsten Ziegeler edited comment on FELIX-4060 at 5/28/14 2:31 PM: -- I've created a branch from the current head at https://svn.apache.org/repos/asf/felix/sandbox/http-rfc189/ and added the current api from RFC 189 (including DTO and annotations from core as those are not available as maven artifacts yet) was (Author: cziegeler): I've created a branch from the current head at https://svn.apache.org/repos/asf/felix/sandbox/http-rfc189/ Implement HTTP Service Update (RFC-189) --- Key: FELIX-4060 URL: https://issues.apache.org/jira/browse/FELIX-4060 Project: Felix Issue Type: New Feature Components: HTTP Service Reporter: Carsten Ziegeler The OSGi early draft 2013-03 contains a version of RFC 189, the HTTP service update. This issue is for keeping track of the changes and their implementations -- This message was sent by Atlassian JIRA (v6.2#6252)
