[
https://issues.apache.org/jira/browse/XBEAN-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892140#action_12892140
]
David Jencks commented on XBEAN-151:
------------------------------------
Hi Ryan,
thanks for looking into this. I'm wondering if you can clear up a couple
points easily..
1. is the spring validation just xml validation against the schema using e.g
the sax parser validation, or is it something else?
2. IIUC, assuming the answer to (1) is "spring validation is xml validation",
even if you supply the schemas to the validator you get errors. Is this
because the schema generated by xbean is wrong or is there some other problem?
In other words, if we modified the "invalid" documents to match the schema
would the errors go away and we could still get the same bean configuration out?
> Xbean-Spring is "incompatible" with Spring Framework 3.0.x
> ----------------------------------------------------------
>
> Key: XBEAN-151
> URL: https://issues.apache.org/jira/browse/XBEAN-151
> Project: XBean
> Issue Type: Bug
> Components: spring
> Environment: Any
> Reporter: Ryan Moquin
> Attachments: ClassPathXmlApplicationContext.java,
> org.apache.xbean.spring.context.RestaurantUsingXBeanTest.txt,
> ResourceXmlApplicationContext.java
>
>
> A lot of people have complained about this but haven't opened an issue for
> it. I've investigate it a bit and really it's not that xbean-spring is truly
> incompatible, it's that everyone (including the spring-xbean unit tests)
> creates xbean-spring configurations that assume Spring validation is turned
> off. This means that an xbean-spring configuration will fail to load without
> the schemaLocation defined with all custom namespaces. This can get a little
> tricky with xbean-spring syntax since when you add the appropriate schemas
> for validation, the xbean-configuration will fail to validate even though the
> configuration loads and operates correctly at runtime. I've found a few
> constructs I've used to be tough to figure out how to get to validate in
> order to run with Spring 3.0.x. The easiest solution to deal with this is to
> something turn off the default validation in Spring 3.0.x (which wasn't
> turned on by default in versions of Spring previous to 3.0.x). To reproduce
> this, simply get the project's code from trunk, and change the spring
> dependency versions to, 3.0.3.RELEASE and build. xbean-spring will fail.
> I'm attaching the results of one of the failed tests and you'll see the xbean
> configuration for that test failed validation for the "beans" tag.
> Here is what the results of the build look like, in case it helps in anyway:
> Results :
> Tests in error:
> testPizza(org.apache.xbean.spring.context.RestaurantUsingXBeanTest)
> testPizza(org.apache.xbean.spring.context.RestaurantUsingXBeanAsRootTest)
> testBeer(org.apache.xbean.spring.context.BeerNullTest)
> testFavs(org.apache.xbean.spring.context.FavoriteUsingXBeanMixedTest)
> testBeer(org.apache.xbean.spring.context.KegXBeanTest)
> testBeer(org.apache.xbean.spring.context.KegXBeanAndPropertiesTest)
>
> testPizza(org.apache.xbean.spring.context.PizzaUsingXBeanWithJavaNamespaceTest)
> testConfigureJndiInsideSpringXml(org.apache.xbean.spring.jndi.JndiTest)
> testBeer(org.apache.xbean.spring.context.BeerUsingXBeanSystemPropTest)
> testPizza(org.apache.xbean.spring.context.PizzaUsingXBeanTest)
>
> testPizza(org.apache.xbean.spring.context.RestaurantUsingXBeanWithSimplerConfigTest)
> testRecipes(org.apache.xbean.spring.context.RecipeUsingXBeanMixedTest)
>
> testPizza(org.apache.xbean.spring.context.RestaurantUsingResourceXmlApplicationContextTest)
> test(org.apache.xbean.spring.context.SpringExtensionTest)
> testSocketService(org.apache.xbean.spring.context.SocketAddressXBeanTest)
> testSocketAddress(org.apache.xbean.spring.context.SocketAddressXBeanTest)
> testRecipes(org.apache.xbean.spring.context.RecipeUsingXBeanTest)
> testFavs(org.apache.xbean.spring.context.FavoriteUsingXBeanTest)
> testBeer(org.apache.xbean.spring.context.BeerUsingXBeanTest)
> testWine(org.apache.xbean.spring.context.WineUsingXBeanTest)
>
> testPizza(org.apache.xbean.spring.context.PizzaUsingXBeanWithPropertiesTextNodeTest)
> testSoup(org.apache.xbean.spring.context.SoupUsingXBeanTest)
> testFlatMap(org.apache.xbean.spring.context.FlatMapTest)
> test1(org.apache.xbean.spring.context.ComponentTest)
> test2(org.apache.xbean.spring.context.ComponentTest)
> testQName(org.apache.xbean.spring.context.QNameUsingXBeanTest)
> testWine(org.apache.xbean.spring.context.GinUsingSpringTest)
> testPizza(org.apache.xbean.spring.context.PizzaUsingXBeanWinBeanRefTest)
> testWine(org.apache.xbean.spring.context.VodkaUsingXBeanTest)
> testSalad(org.apache.xbean.spring.context.SaladUsingXBeanTest)
> testPizza(org.apache.xbean.spring.context.RestaurantUsingXBeanMixedTest)
> testPizza(org.apache.xbean.spring.context.RestaurantUsingSpringExtendedTest)
> Tests run: 58, Failures: 0, Errors: 32, Skipped: 0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
