|
||||||||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||||||||
To unsubscribe from this list please visit:
I always implied with this report, that there is a real incompatibility in JRockit, but that's not the case. XStream is from Java to XML and back. Therefore it expects that a persisted sorted collection is sorted (
XSTR-407). XStream makes a great effort to support JDKs where it is possible to rebuild the original instance without calling the comparator for each element again, especially because it can have other unwanted side-effects. When you add now elements out-of-order manually into the XML representation of such a collection, you risk that the resulting instance is simply in an undefined state. That's exactly what you're facing here. It might be that JRockit 6 is the first JRockit version, where XStream is actually able to rebuild the collection without calling the comparator, but if it works on older versions, it has been pure coincidence.