That's correct. There might be some skeleton jetty modules hanging around in the branch from earlier this year, but I reckon they can be removed.
Jon On 30 Sep 2010 18:47, "David Blevins" <[email protected]> wrote: > > On Sep 29, 2010, at 9:13 AM, Jonathan Gallimore wrote: > >> Hi Jean-Louis, >> >> I've been doing some work on integration with Jetty 7. I currently have >> Jetty and OpenEJB working together in a unit test in the >> openejb-jetty-common module, and this is running one of example war files. >> I've got a fair bit of stuff working - I think most of the JNDI wiring is >> there, and I've done a security service. It still needs to be put into >> standalone Jetty container, and needs a way of installing itself, like the >> Tomcat integration. There's also a few things that won't work yet, like >> webservice support. >> >> I've been a bit stalled on this due to work and other commitments but should >> hopefully get back into the swing of it this weekend and next week. >> >> I'll start putting some issues in Jira for this work so we can keep track of >> how we're getting on. > > This currently only works in trunk, right? In the process of cleaning out "ideas that didn't bear fruit" modules from the 3.1.x branch so we can release that without confusing people with jars that don't really do anything yet. > > > -David > > >> On Wed, Sep 29, 2010 at 10:02 AM, Jean-Louis MONTEIRO < >> [email protected]> wrote: >> >>> >>> Hello guys, >>> >>> Using Jetty is quite convenient to use and faster than Tomcat. >>> Moreover, it's simpler to use with maven. >>> >>> I actually would like to know what is the status of our Jetty integration >>> compared with Tomcat integration. >>> What is supposed to work ... ? >>> >>> Thanks a lot. >>> Jean-Louis >>> -- >>> View this message in context: >>> http://openejb.979440.n4.nabble.com/Jetty-Integration-tp1457408p2718570.html >>> Sent from the OpenEJB Dev mailing list archive at Nabble.com. >>> >
