Re: [jervlet-patch] Make Jervlet-Jetty accept external configurations

peter royal wrote:

> On Nov 16, 2003, at 2:59 PM, Ryan Hoegg wrote:
>
>> I agree 100%.  Johan's code set it as a matter of convenience for 
>> existing jetty configurations who depend on it.  For now, I think one 
>> could just set the property before starting loom.  Going forward, is 
>> there a way for loom to prepare an environment for a SAR, including 
>> its own system properties?
>
>
> Not really, since system properties aren't scoped, they are set 
> container-wide and not per-application. which is unfortunate.

Not even with something magic like classworlds?  Actually I suppose we 
could do it with some AOP trickery too.

>
>> Of course that will be irrelevant as we begin to support other 
>> containers.  Perhaps Johan's suggestion to document the hell out of 
>> it is the best after all :)
>
>
> yup. documentation would work, but i also like Paul's suggestion of 
> just getting alternate ways of configuring the things that are 
> currently only configurable via system props :)
> -pete


I do too, but I would lke to see exactly what in an jetty configuration 
would break without that system property.  Forgive my inexperience with 
jetty, but I haven't used that part of its functionality.  What I am 
concerned about is that perhaps people are using the value of jetty.home 
explicitly in their configuration files, like we do in jelly.

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net



-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl