Re: [Fwd: Jetty & System.properties (change request)]

Paul,

the system property jetty.home is not actually used anywhere
in the Jetty code base.   It is only used to parameterize the
configuration files.

If you are coding directly to the Jetty API, there is little
or no concept of a jetty.home.  Only URL locations of webapplications.

The start.jar mechanism does use jetty.home - but only to assist
the parameterized config files.

I just realize that I have written some code to look for a work
file relative to jetty.home, so I will fix that shortly.

Are you using jetty.xml?

cheers


Paul wrote:
> As you know the "spice" team are working on a servlet container 
> abstraction based on the old Sevak codebase.  The project is going well. 
> We're experiencing some pain with Jettys use of system properties.  Is 
> there a way that we could have (symbolically) some alternate way of 
> telling jetty where its base is :
> 
>  jetty.setJettyHome("d:\fooDir");
> 
> or
> 
>  jetty = new JettyImpl("d:\fooDir");
> 
> The situation we are trying to model is two instances of Jetty in one 
> JVM. For teh sake of argument, they could be in different classloaders 
> and point to different home directories.  Basically system properties is 
> (to quote Peter Royal) a "horrid IoC violation".
> 
> We're not trying to get rid of the system property thing, merely trying 
> to specify an alternate way of passing the info to Jetty.



-- 

/****************************************************************
* www.coredevelopers.net for Open Source training & support.
* Training: J2EE Web/Cluster London Nov 10-13
* --
* Greg Wilkins
* Partner
* Core Developers Network
****************************************************************/




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/