[mod_cluster-dev] Excluded contexts

[Brian Stansberry]

jean-frederic clere wrote:
> Paul Ferraro wrote:
>> 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?
> 
> ROOT corresponds to / so everything will be rooted to JBoss by default. 
> I am not sure that is a good default.
> 

I'm kind of on the fence on this one, but my gut tells me you're right, 
Jean-Frederic.

A possibility for a future enhancement is an API around this such that 
an AS deployer could exclude (or include) a context based on a 
jboss-web.xml config element. Then the default ROOT.war that ships with 
the AS could be configured to exclude itself while user-deployed root 
contexts would be allowed.

That only helps inside the AS though. :(


-- 
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry at redhat.com