Once you register yourself, sso.ops4j.org, you will shortly after have commit rights to SVN. It is 'optimistic' in that people will review the commits, and only yell after the fact, instead of you first having to pester committers with 'patches' to be included.
See the Community section on wiki.ops4j.org for more details and philosophy. -- Niclas On Jul 31, 2009 6:11 AM, "Sten Roger Sandvik" <s...@x3m.com> wrote: Hi again. After some late night thinking I see that Pax Web has alot of the stuff I need to make a robust implementation. The jetty implementation is much more sophisticated than I have implemented so I will take a second look at what will be the best approach. My goals right now is to finished the implementation with the following features: * A jetty implementation that supports Filters and Servlets (Pax Web has this already). * A servlet bridged implementation that supports Filters and Servlets (None exists right now). This will do the same as Equinox Servlet Bridge, but with filter support. * A whiteboard implementation that registers servlets and filters using services (Pax Web has this aldread). So, as you can see, I only need to concentrate on the second part. Has one implementation right now, but will try to integrate this into Pax Web and see how it behaves. Have splitted my own Pax Web "fork" into the following modules: * pax-web-service (service implementation that is common between bridge and jetty) * pax-web-jetty (jetty server implementation) * pax-web-bridge (WAR bridged implementation) You (Alin) mentioned that OPS4J has a low entry barrier regards to the contribution. Can you explain in more detail? /srs On Thu, Jul 30, 2009 at 3:54 AM, Sten Roger Sandvik <s...@x3m.com> wrote: > > Yes, I'm aware that t... _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
