There's obviously been a big focus on Tomcat with the work that's gone on with getting TomEE released and certified. I've always been really keen on getting OpenEJB working with Jetty, and have had a very basic setup working which I have previously used for functional testing: http://openejb.apache.org/functional-testing-with-openejb,-jetty-and-selenium.html
I'd love to work on this some more if there's demand for it. Getting something basic working I suspect wouldn't be too difficult, but getting a certified solution would probably be a lot of work and so would be a longer term goal. Do you need a certified solution or would something more basic be enough to get you going? Jon Sent from my iPad On 1 May 2012, at 13:41, "Will Hoover" <[email protected]> wrote: > Is the initial OpenEJB + Jetty now a dead initiative? > > > > The reason why I ask is because the new embedded feature in Tomcat 7 still > is cumbersome to implement when compared to Jetty. This is especially true > when a "real" embedded solution is desired that does not require a directory > structure to maintain. Jetty allows you to set handlers without designating > a home directory for web applications (which is very convenient when > embedding within Java SE/JavaFX applications). I know Tomcat has done this > for compliance reasons, but just as OpenEJB has revolutionized the EJB world > by features outside the norm, so has Jetty in some respects. Don't get me > wrong, I love Tomcat and use it extensively when applicable, but sometimes > it makes more sense to use Jetty. > > > > >
