> It's not overt in the Tomcat integration code as essentially Tomcat ignores
> .ear files and we come back and pick them up via our regular ear processing
> code.  We unpack the ear and hand the wars back to Tomcat and deploy the
> rest.

This morning when I woke up it hit me that this had to be the type of
action you're taking. Thanks. If this is the case some of our
applications can be hosted on a pure OpenEJB/Tomcat stack. OpenEJB can
do so much. Everytime I try to think of a JavaEE feature not provided
by or possible via OpenEJB I have to think very carefully.

Q

Reply via email to