Glenn Nielsen wrote:
> >From looking at the source it appears that a Context Lifecycle Listener
> can only be configured for a web app Context explicitely in server.xml.
> This doesn't work well when a context is automatically deployed without
> being configured in server.xml. Would it be possible to add the ability
> to configure a default web app context Listener at the Engine and Host
> level that is triggered for all web app contexts if configured at the
> Engine scope, or for all web app contexts for a host if configured at
> the Host scope?
>
A generalization of this concept might be a "default" configuration for an
automatically deployed Context within a particular Host or Engine, so that
you could customize things besides context listeners.
This would be especially valuable if you utilize the automatic "User Web
Applications" support so that URLs like:
http://localhost:8080/~craigmcc/
resolve to my public_html directory. See the "Special Features" section of
the following page from the Catalina configuration docs for more info:
http://jakarta.apache.org/tomcat/jakarta-tomcat-4.0/catalina/docs/config/host.html
Does it make sense to think a little more broadly here?
>
> Regards,
>
> Glenn
>
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
