commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <joerg.schai...@gmx.de>
Subject Re: [configuration] Unexpected behavior
Date Fri, 23 Dec 2005 14:23:31 GMT
Oliver Heger wrote:

> Jorge Ferrer schrieb:
>> Hi,
>> 
>> Just in case someone also applied the proposed woraround, I have found
>> an important secondary effect when calling getProperties() which
>> converts the configuration to a java.util.Properties instance: it uses
>> the CHARACTER_NEVER_USED to serialize every multi-valued property.
>> 
>> As a result, I'm trying to implement a patch to allow disabling
>> DELIMITER parsing for certain configuration. I'm having difficulties
>> as currently the DELIMITER is common for all configurations of the
>> JVM. So I have to change that first to make it per configuration. If
>> I'm able to make it work I'll send a patch.
>> 
> <snip/>
> 
> Jorge,
> 
> there is a Bugzilla ticket that covers this issue:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=35828
> 
> You might want to have a look. A patch to solve this problem would be
> highly appreciated.

I've been bitten by this also this week having LDAP names in the
configuration. Problem is, that my component is also just a library and
will be used in enterprize apps with different wars and compoennts, that
also use c-c. So I cannot just go and set the delimiter to something else,
because I might break other components by chance.

In addition to the bugzilla description, would it make sense to have a mode
that turns off the list capability at all?

- Jörg


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


Mime
View raw message