What? Because marc doesn't like system props (even if that is true) that
means that we get rid of them inside of the server? Whatever...
The new ServerLoader & ServerConfig components make use of system properties
to control config. We should not try to get rid of this, as it is a simple
mechanism to expose the config needed to control how the server starts up.
We can then reuse those properties in config files.
Doesn't anyonr remember that I was trying to get us to do this awhile go? So
we could use ${jboss.server.home.dir} and other properties as anchors and make
our config more adaptable...
--jason
Quoting Sacha Labourey <[EMAIL PROTECTED]>:
> Hello,
>
> The problem I think is that Marc didn't wanted system properties anymore. Is
> that right?
>
> Marc, what was your opinion regarding system properties? Are you still
> against them? Would you mind if we could have some kind of SystemProperty
> MBean that could set such values that could then be used in configurations?
>
> Cheers,
>
>
> Sacha
>
>
>
> > -----Message d'origine-----
> > De : [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]De la part de
> > Jules Gosnell
> > Envoye : lundi, 22 avril 2002 23:09
> > A : Sacha Labourey
> > Cc : Jboss-Dev
> > Objet : 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
>
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
