cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Mazza <glen.ma...@gmail.com>
Subject Re: Metro vs. CXF difference in enumerating schemas within a WSDL
Date Thu, 15 Jul 2010 01:18:55 GMT

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

-- 
View this message in context: http://cxf.547215.n5.nabble.com/Metro-vs-CXF-difference-in-enumerating-schemas-within-a-WSDL-tp1092957p1139524.html
Sent from the cxf-dev mailing list archive at Nabble.com.

Mime
View raw message