tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From freeway <...@qad.com>
Subject Re: How can OpenEJB ignore old webapps in Tomcat?
Date Fri, 29 Jan 2010 16:17:24 GMT

Hi David,

Yes, context.xml is the logical place to configure webapp-specific settings
that OpenEJB needs to see.  I know that OpenEJB uses (or can use) several
other XML files located in the webapp: ejb-jar.xml, persistence.xml,
service-jar.xml.  However, the first two of these files have more specific
purposes and should probably be kept compatible with other application
server environments that use them; and my understanding of service-jar.xml
is that it is intended to specify overrides to internal OpenEJB processing
that most implementers should not need.  The new settings concern the
'context' of how the webapp interoperates with OpenEJB, and that fits nicely
with the purpose of context.xml.

One variation of this approach might be to use context.xml to configure
those libraries to be scanned within the webapp, while using <Tomcat
home>/conf/openejb.xml to specify which webapps should be scanned. 
Implementers could enable/disable the various webapps at a high level and
see the settings in one central location.  Fine-tuning the JARs to be
covered in each webapp would be done separately.  However, this approach has
the disadvantage of splitting what is probably in practice a single
configuration decision into several different places.  So overall, perhaps
your idea is best.

Fred
-- 
View this message in context: http://n4.nabble.com/How-can-OpenEJB-ignore-old-webapps-in-Tomcat-tp1051311p1415638.html
Sent from the OpenEJB User mailing list archive at Nabble.com.

Mime
View raw message