|
||||||||||||||||
|
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:
The primary description of this issue implies the modification of the setup of an XStream instance at (un)marshalling time. This is highly discouraged and not really supported, because XStream uses internal caches, that will not be flushed, if something is changed, and because it is on top not thread-safe at all.
XStream's default mechanism for converters is to override them either with equal or higher priority (the NullConverter is registered as VERY_HIGH). Remember, that a converter provides no information, which types it actually handles therefore it does not make sense to unregister a converter for type X. Nevertheless, you can provide an own implementation of a ConverterRegistry that supports unregistration - you just cannot use the XStream facade.
To support multiple versions of an XML structure, you might transport the version info in the context and use converters that can act on the provided version.