[mod_cluster-dev] Excluded contexts

Paul Ferraro paul.ferraro at redhat.com
Mon Jan 26 11:03:01 EST 2009


On Mon, 2009-01-26 at 16:48 +0100, jean-frederic clere wrote:
> 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?
> 
> Enable ROOT context by default is probably not a good idea. every 
> requests will go to JBoss and probably will return 404.
> 
Why would there be any requests for these webapps via httpd at all?

Imagine the typical use case - most JBoss Web users deploy their web app
using the ROOT context (replacing the one that exists by default).
Should we make the majority of users have to override this property?

> +1 to use a system property :-)
> 
> Cheers
> 
> Jean-Frederic
> 
> > 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 at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/mod_cluster-dev
> > 
> 




More information about the mod_cluster-dev mailing list