But if we add it to the tomcat6-jee5 config.xml, wouldn't that allow a user to set load=false on it if they also disabled the webconsole?

Also, shouldn't we list all installed configurations by default, so users can better understand which ones are being provided by the assembly, like users deploying Daytrader or other end user apps that want to use our provided Dojo files?


-Donald

Paul McMahan wrote:
On 3/20/07, Donald Woods <[EMAIL PROTECTED]> wrote:
Just noticed 2 differences between the current jetty6-jee5 and
tomcat6-jee5 config.xml files and wondered if this was intended?

1) jetty6-jee5 has load=false for the axis car, while tomcat6-jee5 doesn't

2) jetty6-jee5 include the dojo-jetty6 car, but tomcat6-jee5 doesn't
include the dojo-tomcat car

The tomcat/jetty dojo car is automatically started since the
respective tomcat/jetty webconsole car depends on it.   So I would
recommend removing it from the jetty config.xml instead of adding it
to the tomcat config.xml  (maybe that's what you already had in mind)

Best wishes,
Paul


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to