marc fleury wrote:
> OK maybe some of the configuration of Jetty in JBoss will be useful after
> all...
> 
> After all I said about their configuration language... jules please advise

Errrr....

That's it !


Jules

P.S.

Here is an example from a standalone jetty.xml :

   <Call name="addListener">
     <Arg>
       <New class="org.mortbay.http.SocketListener">
         <Set name="Port"><SystemProperty name="jetty.port" 
default="8080"/></Set>
         <Set name="MinThreads">5</Set>
         <Set name="MaxThreads">255</Set>
         <Set name="MaxIdleTimeMs">30000</Set>
         <Set name="MaxReadTimeMs">10000</Set>
         <Set name="MaxStopTimeMs">5000</Set>
         <Set name="LowResourcePersistTimeMs">5000</Set>
       </New>
     </Arg>
   </Call>

This calls a method 'addListener' on the object currently in 'focus' (a 
jetty server) passing in a new Listener.

While the new listener is in 'focus' we 'set' a number of attributes on it.

One of these - the port number, may be overriden by the the sysprop 
jetty.port.

In this way a custom Jetty instance can be bolted together without 
recompilation and parameters can be externalised.

If you want to know anymore - it's Greg's baby and the code is all in 
CVS - I think it is called XmlConfigurator.

P.S.

I guess Greg has all sorts of method resolution and type conversion 
stuff going on behind the scenes. It looks messy, but basically allows 
you to script Java in XML - a very powerful way to configure your app.

> 
> marcf
> 
> |-----Original Message-----
> |From: [EMAIL PROTECTED]
> |[mailto:[EMAIL PROTECTED]]On Behalf Of Jules
> |Gosnell
> |Sent: Monday, April 22, 2002 2:09 PM
> |To: Sacha Labourey
> |Cc: Jboss-Dev
> |Subject: Re: [JBoss-dev] Deployment and config: one more thing, port
> |numbers.
> |
> |
> |Jetty has a useful construct in it's xml config.
> |
> |You can use something like:
> |
> |<arg>
> |  <SystemProperty name="jetty.home"default="./">/config/jetty.xml
> |</arg>
> |
> |Jetty expands all SystemProperty tags accordingly.
> |
> |If we supported some such construct, users could choose what they wanted
> |to externalise (or override) with a properties file.
> |
> |
> |
> |Jules
> |
> |
> |
> |Sacha Labourey wrote:
> |> Hello,
> |>
> |> As the deployer/config issue is very hot these days, I want to add oil on
> |> the fire ;)
> |>
> |> I see an interest in setting port numbers in an external config
> |file (le'ts
> |> say parameters.xml or port.xml, whatever).
> |>
> |> Then we would reference this file from our jboss-services.xml
> |files instead
> |> of disseminating port configuration everywhere in 8 XML files and 3 SARs.
> |> Furthermore (and you will understand why I propose this), if you
> |want to run
> |> 2 JBoss instances on the same IP address, configuration becomes
> |a headache.
> |>
> |> Feel free to complain loudly.
> |>
> |> Cheers,
> |>
> |>
> |>                            Sacha
> |>
> |>
> |> _______________________________________________
> |> 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