Thanks  Emmanuel, I was unsure if the spec limited the integer size or not.

Michael Cugini


Emmanuel Bourg wrote:
> 
> Hi Michael,
> 
> I think that's a bug, the plist spec doesn't limit the size of the 
> integer. We should probably parse the value as a Long or a BigInteger.
> 
> Get a nightly build in a couple of days, I'll fix this issue.
> 
> Emmanuel Bourg
> 
> 
> 
> 
> Michael Cugini a écrit :
>> Hey all,
>> 
>> I've been recently attempting to parse iTunes music library xml plists, 
>> and have run into an issue.  When loading an 
>> XMLPropertyListConfiguration the following exception is thrown:
>> 
>>    org.apache.commons.configuration.ConfigurationException: Unable to 
>> parse the configuration file
>>        at 
>> org.apache.commons.configuration.plist.XMLPropertyListConfiguration.load(XMLPropertyListConfiguration.java:249)
>>  
>> 
>>        .....
>>    Caused by: java.lang.NumberFormatException: For input string: 
>> "3290007019"
>>        at 
>> java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
>>  
>> 
>>        at java.lang.Integer.parseInt(Integer.java:459)
>>        at java.lang.Integer.<init>(Integer.java:620)
>> 
>> The offending line in the XML file is:
>>            <key>Play Date</key><integer>3290007019</integer>
>> 
>> 3290007019 is outside of the range of an int, so I'm guessing that is 
>> the issue.  Is this a case of a malformed plist, or a bug 
>> XMLPropertyListConfiguration?
>> Is there any way I can solve this?
>> 
>> Thanks in advance
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Problem-initializing-XMLPropertyListConfiguration-tp16505252p16568727.html
Sent from the Commons - User mailing list archive at Nabble.com.


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

Reply via email to