Getting ill (?) formatted config back from webapp #3935
-
On several occasions I've seen config in webapp getting somehow messed up and then returned to me via REST with fields like below:
Initially (after a restart and reload) it all looks good, i.e. w/o these idref, Integer0, Integer2 or Boolean0, but after some time and some activity (I'm not quite sure, which one specifically triggers this, they're all like marking projects indexed, getting/setting config and kicking off Suggesters), I start getting the above. This doesn't look like a correct format, right? What could be the reason? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Actually, just querying config a few times is enough to trigger the above output:
So, if I restart Tomcat, wait for it to load and then run the above command, I get this:
But after trying it 6 more times I get this:
|
Beta Was this translation helpful? Give feedback.
-
As long as the configuration can be de-serialized the format is fine. It's the way XML serializer works in Java. The https://docs.oracle.com/javase/7/docs/api/java/beans/XMLEncoder.html says:
Also see https://docs.oracle.com/javase/8/docs/api/javax/xml/bind/annotation/XmlIDREF.html This is just one of the cons of the XML serialization. #2329 tracks the replacement of the serialization scheme. |
Beta Was this translation helpful? Give feedback.
As long as the configuration can be de-serialized the format is fine. It's the way XML serializer works in Java. The
idref
replaces object containment with object reference.https://docs.oracle.com/javase/7/docs/api/java/beans/XMLEncoder.html says:
Also see https://docs.oracle.com/javase/8/docs/api/javax/xml/bind/annotation/XmlIDREF.html
This is just one of the cons of the XML serialization. #2329 tracks the replacement of the serialization scheme.