Romain Manni-Bucau wrote > is it intended it is not the same URLs? (someproject3 vs someproject)
No, that was a typo when I composed this message, sorry. Correct would have been "someproject3" in both URLs, so that they're completely equal, apart from the case. Romain Manni-Bucau wrote > First thing I'd do is to check why the case is different, even if openejb > tries to absorb that it is generally an issue when launching the command > line/created the classpath. I guess the problem is the classloader used by the JUnit runner (windows / Eclipse), which is outside of the OpenEJB ecosystem. Hence, it discovers the lowercased URL from the ejbModule, as well as the not-lowercased URL from the project folder via its eclipse run configuration, which leads to the problem in the validation framework. Romain Manni-Bucau wrote > If still an issue you can probably use as you mentionned arquillian or > ApplicationComposer but EJBContainer normally works when the JVM is not > corrupted (if you use eclipse, give it a try outside eclipse too). I tried executing the tests with maven (surefire plugin), but still the same. Ugly but interesting: I found out that I can get the code working when tricking OpenEJB into thinking it's on a non-windows os, by supplying VM parameters -Dos.name=foo. I have to think about if I want to use that as a strategy, or accept the additional complexity of arquillian or the ApplicationComposer. Anyway: many thanks for supporting! -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/ValidationException-due-to-META-INF-validation-xml-s-url-capitalization-tp4681940p4681948.html Sent from the TomEE Users mailing list archive at Nabble.com.
