![jar of beans 4.3.2 jar of beans 4.3.2](https://docs.wto.org/dol2fe/pages/AutonomyImageProxy.aspx?TargetImage=c9/a239f8/3ac12a94f80be2c3af2c64ac/569376/KV_GENERATED_FILE_0000aa.jpg)
![jar of beans 4.3.2 jar of beans 4.3.2](https://forum.katalon.com/uploads/default/original/2X/5/551d239a2814100366d814da4cc89330a548a404.png)
Without the versions, the value-separator attribute in the property placeholder will cause the following error: .xml.XmlBeanDefinitionStoreException: Line 22 in XML document from class path resource is invalid nested exception is : cvc-complex-type.3.2.2: Attribute 'value-separator' is not allowed to appear in element 'context:property-placeholder'.Īt .(XmlBeanDefinitionReader.java:399) And when my declared XSDs were versionless(sic), I would notice very strange errors. In my case I was developing a stand-alone CLI tool, a jar of jars. I know that the question is over two years old, but my take is to proceed with caution.
![jar of beans 4.3.2 jar of beans 4.3.2](https://www.researchgate.net/profile/Catherine-Bennetau-Pelissero/publication/326481742/figure/fig3/AS:1007738599522307@1617275013134/Classification-of-the-main-legumes-according-to-their-increasing-allergenic-properties_Q320.jpg)
Those XSD files are included in Spring JARs - the "versionless" XSD is mapped to the latest version during the build (see the spring.schemas files that actually make that link).Īlso, the files available online are built the same way (see the "schemaZip" target in the gradle build). That doesn't happen often to say the least.Īnyway the Spring team should drop the versioned schemas for Spring 5.0, see SPR-13499. To my knowledge, there's only one case where you'd want to use specific XSD versions: when trying to use a XML attribute that's been deprecated/modified in a more recent version. If they do, it usually means your app is trying to use a XSD that is more recent than the framework version you're using, or that your IDE/tool is not properly configured. It is recommended to use the "versionless" XSDs, because they're mapped to the current version of the framework you're using in your application.Īpplications and tools should never try to fetch those XSDs from the web, since those schemas are included in the JARs. So, my question is, which style would you use and why? In particular, will the versioned schema become unavailable in the future, and will the non-versioned schema keep compatible with a current application when Spring updates the schema?Ī side question is, where can I find a list of the versioned spring schemas? Note that the spring-beans and spring-context schemas are different in the two examples. For example, sometimes I see something like One thing confuses me is that sometimes I see XML configuration files with versioned schemas, yet sometimes with non-versioned ones.