Nice post! On the JNDI topic, what we did for Tomcat was to bi-
directionally merge the two JNDI trees. Sort of bi-directionally. We
merge out entries straight into tomcat's jndi (see assembly/openejb-
tomcat/openejb-tomcat-catalina/src/main/java/org/apache/openejb/tomcat/
catalina/TomcatJndiBuilder.java)
We also take all Tomcat's resoures and "deploy" them into OpenEJB so
they can be used by EJBs.
For the most part all web stuff will use Tomcat's JNDI impl all EJBs
will use OpenEJB's impl. But for the most part they are sych'ed up.
As you note in your blog post, JNDI presents challenges when trying to
get one server to use another server's impl. It's an almost un-
winnable battle as everyone has their own extensions and oddities.
Anyway, a similar approach for Jetty could work.
-David
On Mar 10, 2010, at 5:04 AM, Stephen Connolly wrote:
Posted some progress on jetty-openejb integration of Transaction
Manager
http://javaadventure.blogspot.com/2010/03/openejb-jetty-and-maven-transaction.html
Having fun getting the JNDI stuff working correctly
-Stephen
On 30 January 2010 16:01, David Blevins <[email protected]>
wrote:
Ok, so Jon had a cool idea of still having just one openejb.war
file which
people could drop into Tomcat *or* Jetty. This would be opposed to
having
one openejb-foo-webapp.war for each integration and making users
download
the specific one they wanted.
This sounded strange to me at first, but in looking at it there'd
only be
150k or so of "unwanted" code which is really nothing. The big
penalty that
most "vendors" face in this scenario is that it's ridiculous to
include
*both* Tomcat and Jetty in the same distribution. But with the way
we do
integration where we are the embedded one and *they* are the "king"
platform, it's simply a non issue. It's the user's choice which
platform
they want to drop OpenEJB into. We just need one webapp that is
capable if
being added to Tomcat or Jetty and we're good to go.
Pretty cool. Love it when things like this happen. A past
decision that
continues to pay off.
Anyway, will still leave the openejb-tomcat-webapp module in place
for now,
but will be adding a more "generic" openejb-webapp module to the
assembly/
section.
-David
