I would prefer to keep any additional configurations that ship with the 
release to a minimum.  I think that three configs: "default", "advanced" 
and "example" will cover what we need and won't add much extra 
confusion.  I expect that clustering would go into the "advanced" 
configuration.

--jason


Peter Fagerlund wrote:

>on 11-04-2 01.21, Jason Dillon at [EMAIL PROTECTED] wrote:
>
>>Do you mean a demo or example configuration for the server?  I think
>>that a demo module under jboss-all is not appropriate, but a demo or
>>example configuration under server/ is certainly do able.  There was
>>talk awhile ago about how to best organize this. I have not implemented
>>anything since there was not a final decision.
>>
>>I suggest we add a "advanced" and "example" config directory under
>>server, probably copying "default" for a base.
>>
>
>exactly ++ also maybe a folder for cluster and the like called extended ?
>... The deployer would need to be aware and ant triggable ...Yes - We talked
>about it some while ago and the concencus was - cool ;-) if that is not
>final . then . Ahhh ...
>
>/peter_f
>
>>--jason
>>
>>
>>Peter Fagerlund wrote:
>>
>>>Are We ready to make a Demo folder in jboss-all/ that BM would copy into
>>>output/*/* where I could with an ant build.xml file build and copy to deploy
>>>... and once in deployed in deploy as a webapp I could edit some source -
>>>save - *bong* - cool ...
>>>
>>>/peter_f
>>>
>>>
>>>_______________________________________________
>>>Jboss-development mailing list
>>>[EMAIL PROTECTED]
>>>https://lists.sourceforge.net/lists/listinfo/jboss-development
>>>
>>
>>
>>_______________________________________________
>>Jboss-development mailing list
>>[EMAIL PROTECTED]
>>https://lists.sourceforge.net/lists/listinfo/jboss-development
>>



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to