Yes, it seems like you should be able to go back and forth. Patches welcome!
ERic > -----Original Message----- > From: Guillaume Nodet [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 12, 2004 1:45 PM > To: Jakarta Commons Users List; [EMAIL PROTECTED] > Subject: RE: [Configuration] Problems with properties containing > integers in the name > > > What i needed is: > * get a string representation of the configuration (you > just point it to > me) > * build a new configuration from this string (we can't pass > it as is in > rmi) > > Regards, > Guillaume > > -----Message d'origine----- > De : Eric Pugh [mailto:[EMAIL PROTECTED] > Envoy� : jeudi 12 f�vrier 2004 13:13 > � : 'Jakarta Commons Users List' > Objet : RE: [Configuration] Problems with properties > containing integers > in the name > > > Check out this method: > > http://jakarta.apache.org/commons/configuration/apidocs/org/ap > ache/commons/c > onfiguration/ConfigurationUtils.html#toString(org.apache.commo > ns.configurati > on.Configuration) > > Eric > > -----Original Message----- > > From: Guillaume Nodet [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, February 11, 2004 2:35 PM > > To: Jakarta Commons Users List > > Subject: RE: [Configuration] Problems with properties containing > > integers in the name > > > > > > I got another problem also. I want to have a string > > representation of the > > configuration without using a temporary file (as the > > Configuration interface > > is not Serializable). I did not see any simple methods get > > this. The load > > and store functions do not accept InputSteam or OuputStream > objects... > > > > Regards, > > Guillaume > > > > -----Message d'origine----- > > De : Guillaume Nodet [mailto:[EMAIL PROTECTED] > > Envoy� : mercredi 11 f�vrier 2004 14:28 > > � : [EMAIL PROTECTED] > > Objet : [Configuration] Problems with properties containing > > integers in > > the name > > > > > > I've tried to use the configuration component but ran into > > the following > > problems. > > I wanted to export a configuration (stored in a .properties > > file) to an xml. > > The problem is that i had some properties like this: > > xxx.yyy.1=zzz1 > > xxx.yyy.2=zzz2 > > ... > > > > Two problems arose: > > * the xml syntax does not support tag beginning by a numeric > > character, > > so the <1>, <2> tags are not valid > > * my list of properties contained more than 10 items and the > > subset method > > returned bad things. The subset method does not check for > > a '.' at the > > end of the prefix, so that xxx.yyy.10.zzz was returned > > when asking for a > > subset > > beginning with 'xxx.yyy.1'. > > > > Regards, > > > > Guillaume Nodet > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
