--- Begin Message ---
True,
But in a distributed cluster, you only want to update Jetty's config in one
place, then when you deploy it, have Jetty and it's config distributed
everywhere.
The jetty.xml is only really a legacy file, which should be merged with the
jetty-plugin.sar/jboss-service.xml anyway - and this lives in the sar.
I don't know, but we should support running unpacked sars - then you could
mess with the descriptor and the thing would reload with its new
configuration.
I appreciate that this may make things a little more awkward in the short term
- but few people will need to mess with the jetty.xml and the webdefault.xml.
What do you reckon?
It seemed so obvious to me that I didn't question it - maybe I have jumped the
gun ?
Jules
Hunter Hillegas wrote:
> I noticed you just checked in changes to have the config be inside the the
> SAR... In this instance, to change jetty's config you would unpack the sar,
> change the file and then repackage it?
>
> --
> Hunter Hillegas
> Chief Technology Officer
> Guerrilla Broadcasting, Inc.
> [EMAIL PROTECTED]
--- End Message ---
