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.
e.g.
<property
name="excludedContexts">${jboss.modcluster.excludedContexts:host1.ROOT,invoker,jbossws,jmx-console,juddi,web-console}</property>
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.
Thoughts?
Paul
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:
<property
name="excludedContexts">ROOT,invoker,jbossws,jmx-console,juddi,web-console</property>
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?
e.g.
<property
name="excludedContexts">${jboss.modcluster.excludedContexts:invoker,jbossws,jmx-console,juddi,web-console}</property>
Thoughts?
Paul
_______________________________________________
mod_cluster-dev mailing list
mod_cluster-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/mod_cluster-dev