geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Boynes" <>
Subject RE: One True Way (TM) of handling configuration files
Date Fri, 08 Aug 2003 16:58:27 GMT
None of these solutions seem to meet all the requirements.

In-archive files are a pita, triply so when the archive is packed.
Out-of-archive files are a pita when you are trying to move an application
through the release process (dev->integrate->test->stage->prod)
One-config-file (a la server.xml) is a pita when you have hundreds of
applications to deploy.

And all of this runs into issues with JSR88 (Deployment) which requires that
the container exposes JavaBeans for manipulating the deployment config
(including the vendor specific part) and uses an API for deployment (rather
than the copy-the-archive-in model typically used today).

JBoss took a two prong approach with its ServiceArchives (SARs) where you
could deploy a .sar archive with embedded metadata
(META-INF/jboss-service.xml) or a standalone metadata file (my-service.xml).
However, one problem not solved to date is of persisting changes to the
configuration so they survive server restarts.

One idea being thrown around was for an external config repository where
runtime changes could be stored - this could be XML files, or could be
plugged to be anything such as a config management system or database.

On deployment, the running configuration would be determined by:
1) the configuration in the repository
2) the configuration in the deployment unit
3) per-server defaults[1]
4) per-domain defaults[1]

Changes an admin made would be stored in the repository. If the deployment
unit was replaced whilst the system was offline, then conflicts would be
need to be resolved before the unit could be started.


[1] see JSR 77 for meaning of server and domain

> -----Original Message-----
> From: Igor Lobanov []
> Sent: Friday, August 08, 2003 3:21 AM
> To:
> Subject: Re: One True Way (TM) of handling configuration files
> Hi Christian and fellow geromimos,
> Friday, August 8, 2003, 2:02:38 PM, you wrote:
> > On Fri, Aug 08, 2003 at 09:44:34AM +0300, Lyytinen Joonas wrote:
> >> Hi,
> >>
> >> One thing that has annoyed me in several app-servers (e.g.
> Weblogic and JBoss) is the
> >> way the server specific configuration XML files located in the
> WARs/JARs/EARs of the
> >> "pure" J2EE application.  This hinders application portability
> and is generally messy.
> >>
> >> My syggeestion is that in geronimo we should adopt a similar
> approach than the Orion
> >> application server (, where the
> implementation specific
> >> files with some default values are generated into a separate
> directory structure
> >> by the application server when a application is deployed on
> the server.
> >> IMHO this has several advantages.
> >>
> >> everyone in favor say ay! :)
> > hi Lyytinen,
> > 1+ for a separate config file, and i think it
> > shoult be only one file (something like Tomcats's server.xml)
> +1 for separate config files
> -1 for only one config file
> It will be pretty much complicated to deploy applications "on hot",
> because deployer component has to open that "applications.xml", add some
> elements and then save it back. On the other hand, if there is
> whole separate configuration directory structure, deployment becomes very
> simple process. You just need to extract your EAR/WAR/JAR to
> applications directory and add one file to corresponding configuration
> folder. Just like Tomcat 5.
> Igor Lobanov

View raw message