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.

 

 

Reply via email to