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
