-
Dec 24th, 2011, 03:06 AM
#1
spring-mongo-1.0.xsd referencing spring-beans-2.5.xsd
http://www.springframework.org/schem...-mongo-1.0.xsd
is still referencing http://www.springframework.org/schem...-beans-2.5.xsd.
Is that really coherent when we know that most VMWare cloudfoundry deployments require/make use of
<beans profile="… ">
which is available only in 3.x xsd ?
Should not better to have two different mongo.xsd to avoid any potential problems using a XSD having a dependency on 2.5 beans format from an applicationContext.xml depending itself on 3.x beans format ?
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules