You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When changing the validationMode to XmlBeanDefinitionReader.VALIDATION_NONE, the context will silently ignore schema-based configuration such as:
<aop:scoped-proxy proxy-target-class="true"/>
whereas this setting should only affect the validation phase and not the semantics of the context IMHO.
This is very likely due to the XmlBeanDefinitionReader.namespaceAware property being set to true for validation modes other than NONE.
This is because of schema namespace awareness having to be explicitly enabled for JAXP parsers: If you turn off schema validation, you'll have to turn on schema namespaces through a dedicated reader.setNamespaceAware(true) call yourself. We are combining those two in a setValidating(boolean) method in other places; I might add that to XmlBeanDefinitionReader itself as well.
Excellent, thank you for the quick reply. It would be great if the behavior you described would be mentioned in the XmlBeanDefinitionReader's javadoc, too.
Olaf Otto opened SPR-6336 and commented
When changing the validationMode to XmlBeanDefinitionReader.VALIDATION_NONE, the context will silently ignore schema-based configuration such as:
<aop:scoped-proxy proxy-target-class="true"/>
whereas this setting should only affect the validation phase and not the semantics of the context IMHO.
This is very likely due to the XmlBeanDefinitionReader.namespaceAware property being set to true for validation modes other than NONE.
Affects: 2.5.6
Attachments:
Referenced from: commits a6bba67
The text was updated successfully, but these errors were encountered: