[
https://issues.apache.org/jira/browse/GEODE-4860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461620#comment-16461620
]
Sai Boorlagadda commented on GEODE-4860:
----------------------------------------
Currently we store XML as a string in the config region and JAXB seems very
liberal, from java docs - Schema validation is not performed on the input XML.
The processing will try to continue even if there are errors in the XML, as
much as possible. Only as the last resort, this method fails with
DataBindingException. So during unmarshalling, Jaxb ignores any XML
element/attribute for which it did not find corresponding fields in POJO and
the other way is trivial from how optional fields are handled.
An extension's XSD is upgradable (addition/deletion of fields) until we store
XML as a string in the config region. When we make efforts to store POJOs into
the config region (and as this is a persistent region) either we need POJOs
implement DataSerializable or use PDX types to be able to recover form disk.
> make sure the extensions xsd is upgradable
> ------------------------------------------
>
> Key: GEODE-4860
> URL: https://issues.apache.org/jira/browse/GEODE-4860
> Project: Geode
> Issue Type: Sub-task
> Components: configuration
> Reporter: Jinmei Liao
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> when other module uses a different version of their own xsd (jdbc-2.0.xsd).
> We should have a strategy to make sure rolling upgrade still work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
