Fwiw, undertow supported is now available in pax-web master branch (6.x).

2015-06-19 12:44 GMT+02:00 Frank Langel <fr...@frankjlangel.com>:

> Thanks. Much appreciated
>
>
> On 6/19/15, 12:36 PM, "Achim Nierbeck" <bcanh...@googlemail.com> wrote:
>
> >Hi Frank,
> >
> >that site is not correct I'll change it asap.
> >Undertow is a special branch made by Harald, and I should have blocked him
> >in doing releases with the Pax-Web Versioning schema.
> >It's been a test only releases that he made to play with Pax CDI on a
> >green
> >field. I did some investigation but the Pax-Web-Undertow branch is
> >in no means compatible to the Pax-Web regular branches.
> >That means till version 4.1.x Pax Web is clean and running with up to
> >Servlet Support 3.1 including White-Board extender (which isn't compatible
> >to the R6 draft of a OSGi specified Whiteboard-Extension for HttpService).
> >With the 5.0 disaster Version 5 is burned for the Pax Web project
> >therefore
> >Version 6.0 (the current master) tries to pick up from the 4.x line with
> >the goal of having a OSGi R6 compliant Whiteboard Extender, which actually
> >removes lot's of the features Pax Web already supports. I'll try my best
> >to
> >have the Old-Pax-Web-Style Whiteboard Extender working the same way it is
> >right now together with a stripped down R6 Compliant Whiteboard Extender.
> >Right now I don't have any plans on adding Undertow support to the master
> >branch. This might be an issue for a future version. Right now only Jetty
> >with all features and Tomcat with a slightly reduced set of features are
> >supported. For production use I still recommend to use Jetty.
> >
> >concerning the undertow-branch and whiteboard support, as I'm not planning
> >in putting any efforts into that branch I doubt there will be any support
> >for it.
> >
> >anyone with free time to spent on adding support for undertow into the Pax
> >Web 6.0.0 (current master) line is more then welcome to do so.
> >As I only work on the Pax-Web project in my spare time (no funding at all)
> >resources are spare and therefore I focus on main issues.
> >
> >regards, Achim
> >
> >
> >2015-06-19 12:06 GMT+02:00 Frank Langel <fr...@frankjlangel.com>:
> >
> >> Thanks a lot for the quick response.
> >> - looking at the features file is a good suggestion, I should have
> >>thought
> >> of it in the first place
> >> - I like to use and test undertow, so my understanding is I need to use
> >>MX
> >> branch, which doesn¹t contain whiteboard extender which stops my bundles
> >> from working
> >>
> >> Allow the following questions
> >> 1. Will the whiteboard extender be included in the MX Branch going
> >>forward?
> >> 2. What is the future of pax web 5+. As per the website, it says that v5
> >> and later, pax web will standardize on undertow. Is that understanding
> >>of
> >> mine correct?
> >>
> >> Thanks
> >> Frank
> >>
> >>
> >> On 6/19/15, 10:41 AM, "Achim Nierbeck" <bcanh...@googlemail.com> wrote:
> >>
> >> >Hi,
> >> >
> >> >first of all Pax-Web 5.0.0-SNAPSHOT and Pax-Web 5.0.0.Mx are
> different.
> >> >The Mx ones are the undertow branches which unfortunately got the
> >>version
> >> >and are completely different to the other versions of Pax-Web.
> >> >One big difference that branch is missing the well-known Whiteboard
> >> >Extender of the regular Pax-Web line.
> >> >Just one note, due to this the current Master of Pax-Web is version 6.0
> >> >and
> >> >currently there is no plan on merging the undertow branch in to master.
> >> >So please beware in case you are betting on Undertow, you run without
> >> >support on it.
> >> >
> >> >Second, as all of the Pax-Web modules are usually tested with Pax-Exam,
> >> >they are known to work with different OSGi runtimes.
> >> >So Felix and Equinox both run fine with Pax-Web.
> >> >
> >> >For a list of dependent bundles, take a look at the Karaf Features
> >> >descriptor, it explicitly tells you which bundles are needed.
> >> >
> >> >Regards, Achim
> >> >
> >> >
> >> >2015-06-19 10:25 GMT+02:00 Jean-Baptiste Onofré <j...@nanthrax.net>:
> >> >
> >> >> You mean Pax Web 5.0.0-SNAPSHOT ?
> >> >>
> >> >> Regards
> >> >> JB
> >> >>
> >> >>
> >> >> On 06/19/2015 10:21 AM, Frank Langel wrote:
> >> >>
> >> >>> Hi,
> >> >>>
> >> >>> Has anyone succeeded running PaxWeb 5.0 on Felix ? I am sure its
> >> >>>doable,
> >> >>> but
> >> >>> I was wondering if someone has made some notes (i.e. list of
> >>dependent
> >> >>> bundles) to ease the installation process.
> >> >>>
> >> >>> Thanks in advance
> >> >>> Frank
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >> --
> >> >> Jean-Baptiste Onofré
> >> >> jbono...@apache.org
> >> >> http://blog.nanthrax.net
> >> >> Talend - http://www.talend.com
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> >> >> For additional commands, e-mail: users-h...@felix.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >> >--
> >> >
> >> >Apache Member
> >> >Apache Karaf <http://karaf.apache.org/> Committer & PMC
> >> >OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> >>Committer &
> >> >Project Lead
> >> >blog <http://notizblog.nierbeck.de/>
> >> >Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
> >> >
> >> >Software Architect / Project Manager / Scrum Master
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> >> For additional commands, e-mail: users-h...@felix.apache.org
> >>
> >>
> >
> >
> >--
> >
> >Apache Member
> >Apache Karaf <http://karaf.apache.org/> Committer & PMC
> >OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> >Project Lead
> >blog <http://notizblog.nierbeck.de/>
> >Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
> >
> >Software Architect / Project Manager / Scrum Master
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> For additional commands, e-mail: users-h...@felix.apache.org
>
>

Reply via email to