It also occurs to me that determining which contexts to exclude from
httpd auto-registration based on the context path alone is not
sufficient. This really needs to be host-qualified.
This would define the invoker,jbossws,jmx-console,juddi,web-console
contexts from the default host, as well as the root context from host1,
but *not* the root context from the default host.
On Mon, 2009-01-26 at 10:28 -0500, Paul Ferraro wrote:
> 1.0.0.Beta3 adds a new excludedContexts configuration property that
> defines a comma delimited list of web contexts that should *not*
> auto-register with httpd. Does anyone have any suggestions/comments
> about which contexts to disable by default? Currently, this property
> defaults to:
> i.e. all contexts deployed by default in the JBoss AS all profile.
> As I think about this more, I think we should use a system property for
> this instead - and perhaps enable the ROOT context by default?
> mod_cluster-dev mailing list
mod_cluster-dev mailing list
Lead, AS Clustering
JBoss, a division of Red Hat