Oops! My answer to your proposal was indeed too fast, as what you proposed
doesn't fix the problem we're facing by camel-msv.
Again, the problem is *not* MSV itself but the *bridge* [1] Kohsuke
Kawaguchi has provided for it:
<groupId>org.iso_relax.verifier.jaxp.validation</groupId>
<artifactId>isorelax-jaxp-bridge</artifactId>
In order to use MSV as a RELAX NG validator through the *standard* Java
Validation API which is part of JAXP. And now the problem is that the
isorelax-jaxp-bridge POM is *not* POM 4.0.0 complaint!
I took a look at the CXF code itself and there MSV is triggered through the
Woodstox which is huge difference to how MSV is triggered inside Camel ;-)
[1]
http://weblogs.java.net/blog/2006/02/10/validate-xml-using-relax-ng-and-jaxp-13
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/About-Camel-source-which-doesn-t-build-under-Maven-3-0-4-tp5517301p5521822.html
Sent from the Camel Development mailing list archive at Nabble.com.
