Re: Felix HttpService improvement...
Hi, I would welcome a one-stop-shop solution for a standalone and bridged environment. Currently, in Apache Sling, we are using either the standalone Jetty based implementation or the Eclipse bridge depending on how we build. Having a single-solution might come very handy. So to second Richard, I suggest you create a JIRA (ensure to check the "ASF inclusion permission box" when uploading the tar or patch) so that we can have a look and then discuss on how to proceed ? Thanks and Regards Felix Richard S. Hall schrieb: > I would certainly be happy to consider it for a replacement to the > existing impl. However, since I am not a big user of the existing impl > (even though I started it a long, long time ago), I guess we need to > hear from people who work and rely on the current impl. > > What would be cool, is if you could create a tar ball and make it > available so people could play with it. You could always create a JIRA > issue and attach it to that...that's the best way to get the ball > rolling to see if there is interest here for accepting it as a > contribution. > > Thanks. > > -> richard > > On 7/26/09 4:13 PM, Sten Roger Sandvik wrote: >> Hi. >> >> I have looked at the HttpService implementation in Felix and I had some >> thoughts on how to improve the functionality. Over the past year I have >> looked long and hard for a solution that has the following features: >> >>* Run inside a WAR on a 3rd part container. >>* Run stand-alone (using jetty). >>* Has servlet filter support. >>* Using whiteboard pattern for registering servlets / filters. >> >> The road led me to Pax Web (supports filters, but only as a stand-alone >> service) and Equinox Servlet Bridge (does not support filters). >> Whiteboard >> registering pattern is implemented by the Pax guys, but does not support >> filters inside a "bridged" environment. >> >> So, eventually I was tired of looking for a solution out there and >> created >> my own. This supports servlets and filters in both stand-alone and >> bridged >> mode (WAR). Now I have come to a fork in the road. Should I donate the >> code >> or host my own. I prefer to donate the code. But is the right place under >> Felix umbrella or Pax Web umbrella? I see that more and more is created >> under Felix and this implementation would be (in my opinion) a great >> addition. >> >> So, what do you guys think? >> >> BR, >> Sten Roger Sandvik >> >> >
Re: Felix HttpService improvement...
I would certainly be happy to consider it for a replacement to the existing impl. However, since I am not a big user of the existing impl (even though I started it a long, long time ago), I guess we need to hear from people who work and rely on the current impl. What would be cool, is if you could create a tar ball and make it available so people could play with it. You could always create a JIRA issue and attach it to that...that's the best way to get the ball rolling to see if there is interest here for accepting it as a contribution. Thanks. -> richard On 7/26/09 4:13 PM, Sten Roger Sandvik wrote: Hi. I have looked at the HttpService implementation in Felix and I had some thoughts on how to improve the functionality. Over the past year I have looked long and hard for a solution that has the following features: * Run inside a WAR on a 3rd part container. * Run stand-alone (using jetty). * Has servlet filter support. * Using whiteboard pattern for registering servlets / filters. The road led me to Pax Web (supports filters, but only as a stand-alone service) and Equinox Servlet Bridge (does not support filters). Whiteboard registering pattern is implemented by the Pax guys, but does not support filters inside a "bridged" environment. So, eventually I was tired of looking for a solution out there and created my own. This supports servlets and filters in both stand-alone and bridged mode (WAR). Now I have come to a fork in the road. Should I donate the code or host my own. I prefer to donate the code. But is the right place under Felix umbrella or Pax Web umbrella? I see that more and more is created under Felix and this implementation would be (in my opinion) a great addition. So, what do you guys think? BR, Sten Roger Sandvik
[jira] Commented: (FELIX-1205) Update to the latest OSGi R4.2 API
[ https://issues.apache.org/jira/browse/FELIX-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735423#action_12735423 ] Guillaume Nodet commented on FELIX-1205: I've fixed the exported versions which were wrong for the core module. > Update to the latest OSGi R4.2 API > -- > > Key: FELIX-1205 > URL: https://issues.apache.org/jira/browse/FELIX-1205 > Project: Felix > Issue Type: New Feature > Components: Framework, Specification compliance >Reporter: Richard S. Hall >Assignee: Richard S. Hall > Fix For: felix-2.0.0 > > > We need to update to the latest OSGi API, which is now frozen for the R4.2 > release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Felix HttpService improvement...
Hi. I have looked at the HttpService implementation in Felix and I had some thoughts on how to improve the functionality. Over the past year I have looked long and hard for a solution that has the following features: * Run inside a WAR on a 3rd part container. * Run stand-alone (using jetty). * Has servlet filter support. * Using whiteboard pattern for registering servlets / filters. The road led me to Pax Web (supports filters, but only as a stand-alone service) and Equinox Servlet Bridge (does not support filters). Whiteboard registering pattern is implemented by the Pax guys, but does not support filters inside a "bridged" environment. So, eventually I was tired of looking for a solution out there and created my own. This supports servlets and filters in both stand-alone and bridged mode (WAR). Now I have come to a fork in the road. Should I donate the code or host my own. I prefer to donate the code. But is the right place under Felix umbrella or Pax Web umbrella? I see that more and more is created under Felix and this implementation would be (in my opinion) a great addition. So, what do you guys think? BR, Sten Roger Sandvik
