Details
-
Type:
Bug
-
Status:
Closed
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
The following stacktrace appears when de-serializing XML file with Java 5.0 new changes in class being saved:
[Fatal Error] :1:1: Content is not allowed in prolog.
Exception in thread "main" com.thoughtworks.xstream.io.StreamException: Content is not allowed in prolog.
at com.thoughtworks.xstream.io.xml.DomDriver.createReader(Unknown Source)
at com.thoughtworks.xstream.XStream.fromXML(Unknown Source)
at com.thoughtworks.xstream.XStream.fromXML(Unknown Source)
at com.aep.tools.persist.XMLSerializer.load(XMLSerializer.java:48)
at com.aep.tools.app.FileStatus.testLoadPersistence(FileStatus.java:505)
at com.aep.tools.app.FileStatus.main(FileStatus.java:544)
XML saved to disk looks like: (partial)
...
<sSize>561152</sSize>
<status>
<_DOLLAR_name>unknown</_DOLLAR_name>
<_DOLLAR_ordinal>3</_DOLLAR_ordinal>
</status>
<sCheckoutStatus></sCheckoutStatus>
</memberProperties>
</com.aep.tools.app.ProjectFile>
<com.aep.tools.app.ProjectFile>
<bIsProject>false</bIsProject>
<sName>Arrpc45.dll</sName>
<memberProperties>
<sVersion>1</sVersion>
<sLastDate>8/25/04 6:48a</sLastDate>
<sType>Binary</sType>
<sSize>131072</sSize>
<status reference="../../../com.aep.tools.app.ProjectFile/memberProperties/status"/>
<status> field shows strange type information on 1st occurrence, and bad reference on 2-n.
Activity
Is the enum converter you spoke of handled by XSTR-70 ?
If not, I would take a crack at it ... where to start ?
Peter Kasson
added a comment - Is the enum converter you spoke of handled by XSTR-70 ?
If not, I would take a crack at it ... where to start ? Yes, that's the one I'm thinking of. Although I haven't tried it yet, so I have no idea if it will actually do what you want.
Joe Walnes
added a comment - Yes, that's the one I'm thinking of. Although I haven't tried it yet, so I have no idea if it will actually do what you want. I've closed this issue as it will be handled by XSTR-70, to reduce duplication and confusion.
Joe Walnes
added a comment - I've closed this issue as it will be handled by XSTR-70 , to reduce duplication and confusion. I am using JDK 1.4.2
I am converting a SOAP response object into an XML file.
I am getting the same output as above in my XML:
<xyz> field shows strange type information on 1st occurrence, and bad reference on 2-n.
The data for that field is in an Object that list all the values like:
public static String _abc = "_abc"
public static String _fgh = "_fgh"
Any idea guys?
Jonathan Shuali
added a comment - I am using JDK 1.4.2
I am converting a SOAP response object into an XML file.
I am getting the same output as above in my XML:
<xyz> field shows strange type information on 1st occurrence, and bad reference on 2-n.
The data for that field is in an Object that list all the values like:
public static String _abc = "_abc"
public static String _fgh = "_fgh"
Any idea guys? @Jonathan: Please, this is not a mailing list! Your case has absolutely nothing to do with enums of JDK 1.5. For questions or problems subscribe to the user list.
Jörg Schaible
added a comment - @Jonathan: Please, this is not a mailing list! Your case has absolutely nothing to do with enums of JDK 1.5. For questions or problems subscribe to the user list. 
I shall try and get an EnumConverter in the next release. In the mean time, your welcome to try to write one yourself. I suggest extended AbstractBasicConverter as a starting point.