Re: [VOTE] Release Apache Felix Http 2.4.0
+1 (non-binding) Chetan Mehrotra On Sun, Feb 1, 2015 at 9:55 PM, Pierre De Rop wrote: > +1 > > regards; > /Pierre > > On Thu, Jan 29, 2015 at 1:51 PM, Carsten Ziegeler > wrote: > >> Hi, >> >> We solved 3 issues in this release, the most important one is the update >> to Jetty 9 >> >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12327075 >> >> This release includes only the changed modules compared to the 2.3.2 >> release. >> >> Staging repository: >> https://repository.apache.org/content/repositories/orgapachefelix-1051/ >> >> You can use this UNIX script to download the release and verify the >> signatures: >> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh >> >> Usage: >> sh check_staged_release.sh 1051 /tmp/felix-staging >> >> Please vote to approve this release: >> >> [ ] +1 Approve the release >> [ ] -1 Veto the release (please provide specific comments) >> >> This vote will be open for at least 72 hours. >> >> Regards >> Carsten >> -- >> Carsten Ziegeler >> Adobe Research Switzerland >> cziege...@apache.org >>
[jira] [Created] (FELIX-4782) Implement session handling
Carsten Ziegeler created FELIX-4782: --- Summary: Implement session handling Key: FELIX-4782 URL: https://issues.apache.org/jira/browse/FELIX-4782 Project: Felix Issue Type: Sub-task Components: HTTP Service Reporter: Carsten Ziegeler Fix For: http-next For RFC 189 a separate session (or attribute map) needs to be managed per ServletContextHelper. In addition, session cookie handling needs to be manageable per ServletContextHelper as well -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4781) Implement various listeners
Carsten Ziegeler created FELIX-4781: --- Summary: Implement various listeners Key: FELIX-4781 URL: https://issues.apache.org/jira/browse/FELIX-4781 Project: Felix Issue Type: Sub-task Components: HTTP Service Reporter: Carsten Ziegeler Fix For: http-next For RFC189 only ServletContextListener and ServletContextAttributeListener are implemented atm, all other listeners need to be implemented -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] Release Apache Felix Http 2.4.0
+1 regards; /Pierre On Thu, Jan 29, 2015 at 1:51 PM, Carsten Ziegeler wrote: > Hi, > > We solved 3 issues in this release, the most important one is the update > to Jetty 9 > > https://issues.apache.org/jira/browse/FELIX/fixforversion/12327075 > > This release includes only the changed modules compared to the 2.3.2 > release. > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1051/ > > You can use this UNIX script to download the release and verify the > signatures: > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > > Usage: > sh check_staged_release.sh 1051 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > Regards > Carsten > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org >
[jira] [Created] (FELIX-4780) [RFC189] Revisit error page implementation
Carsten Ziegeler created FELIX-4780: --- Summary: [RFC189] Revisit error page implementation Key: FELIX-4780 URL: https://issues.apache.org/jira/browse/FELIX-4780 Project: Felix Issue Type: Sub-task Components: HTTP Service Reporter: Carsten Ziegeler Fix For: http-next The error handler is currently registered in the Jetty module and this one calls the DispatcherServlet.handleError. I think the error handlering should directly take place in the base module as we need to maintain the context of the original request, so only error handlers for the same ServletContextHelper should be called -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FELIX-4541) Add support for multiple patterns in servlet/filter registration
[ https://issues.apache.org/jira/browse/FELIX-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14300237#comment-14300237 ] Carsten Ziegeler commented on FELIX-4541: - Same is true for error pages. > Add support for multiple patterns in servlet/filter registration > > > Key: FELIX-4541 > URL: https://issues.apache.org/jira/browse/FELIX-4541 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: J.W. Janssen > Fix For: http-next > > > RFC-189 allows servlets and filters to be registered with multiple paths (and > even regex's for filters). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FELIX-4548) Implement the missing errors registration
[ https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4548. - Resolution: Fixed Merged changes to dispatcher and Jetty module to trunk; error handling is back again > Implement the missing errors registration > - > > Key: FELIX-4548 > URL: https://issues.apache.org/jira/browse/FELIX-4548 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi >Assignee: Carsten Ziegeler > Fix For: http-next > > Attachments: FELIX-4548.patch > > > Current implementation of RFC189 does not support yet errors registration. > Questions are: > * do we want to have a servlet (or maybe a filter fits better) > implementation which serves a static file whenever an HTTP error is detected? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FELIX-4548) Implement the missing errors registration
[ https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-4548: --- Assignee: Carsten Ziegeler > Implement the missing errors registration > - > > Key: FELIX-4548 > URL: https://issues.apache.org/jira/browse/FELIX-4548 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi >Assignee: Carsten Ziegeler > Fix For: http-next > > Attachments: FELIX-4548.patch > > > Current implementation of RFC189 does not support yet errors registration. > Questions are: > * do we want to have a servlet (or maybe a filter fits better) > implementation which serves a static file whenever an HTTP error is detected? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4543) Update webconsole plugin
[ https://issues.apache.org/jira/browse/FELIX-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4543: Fix Version/s: http-next > Update webconsole plugin > > > Key: FELIX-4543 > URL: https://issues.apache.org/jira/browse/FELIX-4543 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: J.W. Janssen > Fix For: http-next > > > Update the webconsole plugin to use the new Http Service API for its output. > It could simply use the HttpServiceRuntime + DTOs for this... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4546) Implement HttpServiceRuntime service
[ https://issues.apache.org/jira/browse/FELIX-4546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4546: Fix Version/s: http-next > Implement HttpServiceRuntime service > > > Key: FELIX-4546 > URL: https://issues.apache.org/jira/browse/FELIX-4546 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: David Bosschaert > Fix For: http-next > > Attachments: patch.txt > > > Implement the Http Service Runtime service as described in RFC 189 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4100) Support osgi.http.whiteboard.target whiteboard property
[ https://issues.apache.org/jira/browse/FELIX-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4100: Fix Version/s: http-next > Support osgi.http.whiteboard.target whiteboard property > --- > > Key: FELIX-4100 > URL: https://issues.apache.org/jira/browse/FELIX-4100 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.2.0 >Reporter: Mike Wilson >Assignee: J.W. Janssen > Fix For: http-next > > > Consider an OSGi system running the Felix HTTP whiteboard service and > multiple HttpServices. > Currently it is not possible to control which HttpService the Felix > whiteboard binds to for registering servlets. We get random binding > behaviour. It would be natural to provide a configuration setting for the > whiteboard that allows to specify a standard OSGi filter to refer to the > desired HttpService. > This filter could then be used when calling superclass constructors from > org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker. > It might also be appropriate to integrate the configuration setting with the > standard ConfigurationAdmin service (this may deserve its own JIRA ticket > though). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-1651) Support * in servlet registrations
[ https://issues.apache.org/jira/browse/FELIX-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-1651: Fix Version/s: http-next > 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 >Assignee: J.W. Janssen > Fix For: http-next > > > 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.3.4#6332)
[jira] [Updated] (FELIX-2137) Make it possible to set servlet/filter name
[ https://issues.apache.org/jira/browse/FELIX-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-2137: Fix Version/s: http-next > Make it possible to set servlet/filter name > --- > > Key: FELIX-2137 > URL: https://issues.apache.org/jira/browse/FELIX-2137 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Sten Roger Sandvik >Assignee: J.W. Janssen > Fix For: http-next > > > Setting the name of a servlet is useful in some cases. Right now it is > setting the servlet name as "servlet-#" where # is a instance number. The > same as filter. Setting the name of a servlet/filter could be done in two > ways: > * Setting a service property (lile "name") -> only possible when using > whiteboard implementation. > * Setting it as a special init property -> can be done either using > whiteboard or HttpService. Probably the best approach. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4779) Improve request dispatching
Carsten Ziegeler created FELIX-4779: --- Summary: Improve request dispatching Key: FELIX-4779 URL: https://issues.apache.org/jira/browse/FELIX-4779 Project: Felix Issue Type: Sub-task Components: HTTP Service Reporter: Carsten Ziegeler Fix For: http-next Right now all services (especially filters) are matched against the request, we could improve this -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (FELIX-4548) Implement the missing errors registration
[ https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reopened FELIX-4548: - Assignee: (was: J.W. Janssen) It seems error registration is currently not working, at least the OSGi ct tests fail > Implement the missing errors registration > - > > Key: FELIX-4548 > URL: https://issues.apache.org/jira/browse/FELIX-4548 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Affects Versions: http-2.4.0 >Reporter: Simone Tripodi > Fix For: http-next > > Attachments: FELIX-4548.patch > > > Current implementation of RFC189 does not support yet errors registration. > Questions are: > * do we want to have a servlet (or maybe a filter fits better) > implementation which serves a static file whenever an HTTP error is detected? > or > * looking for a solution that delegates the underlying servlet container? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FELIX-4541) Add support for multiple patterns in servlet/filter registration
[ https://issues.apache.org/jira/browse/FELIX-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-4541: --- Assignee: (was: J.W. Janssen) The registration is not handled according to the spec: if there are multiple servlets for the same pattern, the one with the highest service ranking is registered. if a servlet specifies multiple patterns, it might only be registered for some of them, as other servlets with a higher ranking overlay a set of patterns > Add support for multiple patterns in servlet/filter registration > > > Key: FELIX-4541 > URL: https://issues.apache.org/jira/browse/FELIX-4541 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: J.W. Janssen > Fix For: http-next > > > RFC-189 allows servlets and filters to be registered with multiple paths (and > even regex's for filters). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FELIX-4541) Add support for multiple patterns in servlet/filter registration
[ https://issues.apache.org/jira/browse/FELIX-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-4541: Fix Version/s: http-next > Add support for multiple patterns in servlet/filter registration > > > Key: FELIX-4541 > URL: https://issues.apache.org/jira/browse/FELIX-4541 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: J.W. Janssen >Assignee: J.W. Janssen > Fix For: http-next > > > RFC-189 allows servlets and filters to be registered with multiple paths (and > even regex's for filters). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (FELIX-4541) Add support for multiple patterns in servlet/filter registration
[ https://issues.apache.org/jira/browse/FELIX-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reopened FELIX-4541: - > Add support for multiple patterns in servlet/filter registration > > > Key: FELIX-4541 > URL: https://issues.apache.org/jira/browse/FELIX-4541 > Project: Felix > Issue Type: Sub-task > Components: HTTP Service >Reporter: J.W. Janssen >Assignee: J.W. Janssen > Fix For: http-next > > > RFC-189 allows servlets and filters to be registered with multiple paths (and > even regex's for filters). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FELIX-4778) Implement ordering of ServletContextHelper
Carsten Ziegeler created FELIX-4778: --- Summary: Implement ordering of ServletContextHelper Key: FELIX-4778 URL: https://issues.apache.org/jira/browse/FELIX-4778 Project: Felix Issue Type: Sub-task Components: HTTP Service Reporter: Carsten Ziegeler Fix For: http-next Right now, the prefix and ranking of a ServletContextHelper is not correctly considered for request processing. If a request is received, the ServletContextHelper with the longest matchin prefix should process the request first. If there is more than one SCH with the same prefix, they are processed based on their ServiceReference ordering (highest ranking first). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
