Giacomo Pati wrote:
> 
> Quoting Sylvain Wallez <[EMAIL PROTECTED]>:
> 
<snip/>
> > > > 3) Copies the initialization parameters into a Map (generic java
> > object).
> > >
> > > This is to generalize the ServletConfig (and any other environment
> > > specifiy configuration methods/objects) into simple name/value pairs?
> >
> > I once proposed to be able to "externalize" some of the values in
> > cocoon.xconf using a substitution syntax like "${name}". The purpose is
> > to avoid modifying cocoon.xconf during deployment (e.g. jdbc URLs, cache
> > sizes, etc). It seems like these values could be fetched from these
> > initialization parameters.
> 
> I don't see how this relates. The mentioned Map contains the name/values
> specified in the web.xml file. There is no such things like pool sizes, dburls
> etc.
> 
OK, maybe I wasn't clear : I would like the ability of some component
configuration values to be expressed in web.xml or other name/value
pairs sources such as property files. The purpose is to be able to set
some configuration values related to deployment without having to touch
cocoon.xconf.

For example, this would allow the following :
In web.xml :
...
  <init-param>
    <param-name>personnel-db-url</param-name>
    <param-value>jdbc:oracle:thin:@host:1521:sid</param-value>
  </init-param>
  <init-param>
    <param-name>personnel-db-maxconnections</param-name>
    <param-value>15</param-value>
  </init-param>
...

In cocoon.xconf :
...
  <datasources>
    <jdbc name="personnel">
      ...
      <pool-controller min="5" max="${personnel-db-maxconnections}"/>
      <dburl>${personnel-db-url}</dburl>
    </jdbc>
  </datasources>
...

By (bad) experience, I know that there are some customers sysadmins that
install applications we've made for them who don't even know what a
valid XML file is ! They're skilled to the GUI of their application
server, but don't like manual editing of cryptic configuration files.

This feature would allow them to set the values for the configuration
that they have to set, and only these ones, without allowing them to
change values they shouldn't modify or break the whole app by
accidentally erasing a ">" in cocoon.xconf.

<snip/>

> > > Giacomo (yes, I'm back from vacation but still some hundered mails
> > > away from the head :/ ).
> >
> > Still on vacation, and it's still raining :(
> 
> I feel sorry for you.
> 
Thanks, but, well, it gives me some time to improve my Cocoon and Avalon
knowledge :)

-- 
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to