No, this is something controlled by the framework. For us, its:
rt/core/src/main/java/org/apache/cxf/wsdl11/SchemaUtil.java line 126. When we feed the schemas into JAXB, we have to have unique SystemID's assigned to them so the schemaLocations can match up. We chose one way, they apparently chose a different way. :-( Dan On Wednesday 14 July 2010 9:18:55 pm Glen Mazza wrote: > Umm, I think there's a solution here: > > mybindingfile.xjb: > <!--CXF --> > <jaxb:bindings schemaLocation="ShoppingService.wsdl#types1" > node="/xs:schema"> > <!--Metro --> > <jaxb:bindings schemaLocation="ShoppingService.wsdl#types?schema1" > node="/xs:schema"> > > May I say that in all likelihood, the problem is that the XJC version used > by CXF's codegen plugin and the XJC version used by Metro's Maven plugin is > just different, and they interpret the schemaLocations in the JAXB binding > file differently? Stated another way, CXF has *nothing* to do with the > parsing or syntax of the schemaLocation values in the JAXB binding file--it > just feeds the file to XJC for the latter to either accept or complain > based on the particular XJC version's syntax? > > Glen -- Daniel Kulp dk...@apache.org http://dankulp.com/blog
