Hi.. Could you file a bug for this? A failing unit test would be even better. As far as the XML, are you saying that in xml, this is a valid tag: <myTag> but this is not: <1myTag> or <1>?
Odd, but if that is true, we should document that short coming. In terms of fixing it, I don't think their is anything to do... As far as your subset problem, could you submit a test case? Not quite sure I understand what the problem is... Eric > -----Original Message----- > From: Guillaume Nodet [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 11, 2004 2:28 PM > To: [EMAIL PROTECTED] > Subject: [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]
