commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Fiol BonnĂ­n <antonio.f...@gmail.com>
Subject Re: [configuration]Problems with XMLConfiguration
Date Fri, 10 Sep 2004 15:24:12 GMT
I'd be happy if it were "."

Otherwise, why would I use

prop.name.1
prop.name.2

if it were not to create a list?


Antonio Fiol

On Thu, 9 Sep 2004 10:16:22 +0000 (UTC), Henning P. Schmiedehausen
<hps@intermeta.de> wrote:
> =?ISO-8859-1?Q?Antonio_Fiol_Bonn=EDn?= <antonio.fiol@gmail.com> writes:
> 
> Just a wild thought but to solve this problem for JNDI, we could e.g.
> add a kludge to c-c which allows
> 
> xxxx_1
> xxxx_2
> xxxx_3
> 
> to be folded onto a List for get("xxxx");
> 
> Maybe using something more unique than just "_" as a marker.
> 
>         Regards
>                 Henning
> 
> 
> 
> 
> >Maybe this belongs more to -user than to -dev, but please forgive me
> >as this started here.
> 
> >> > 1.- Is it possible to have two properties at the same point? How?
> >
> >> I don't think it's possible.
> >
> >> > Otherwise, is there a point for getList with JNDI?
> >
> >> A List could be directly stored in the repository.
> 
> >How?
> 
> >IIRC, only simple types can be configured, at least in Tomcat.
> 
> >> Parsing the keys of the "conf" subset could be a solution but it's still
> >> complicated. This may be easier once we refactor the code for
> >> hierarchical configurations around the version 2.0.
> 
> >Yes, or maybe adding a list of names in the configuration (as multiple
> >properties in XML or a single comma-separated property in JNDI).
> 
> >> I'm not convinced [configuration] is the right tool for complex
> >> configurations, I tend to prefer [digester] in these cases.
> 
> >What about JNDI and mixing configuration sources? Does [digester] support those?
> 
> >Thank you very much,
> 
> >Antonio Fiol

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message