cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Mazza <>
Subject Metro vs. CXF difference in enumerating schemas within a WSDL
Date Wed, 14 Jul 2010 17:56:55 GMT

Team, I recently noticed a problem perhaps related to Tom's[1] regarding the
schemaLocation value in a JAXB binding file[2].  CXF enumerates schemas
using Schema Component Descriptors (SCD's) within a WSDL differently from
Metro, resulting in JAXB binding files being incompatible between the two:

   <!--CXF -->
   <jaxb:bindings schemaLocation="ShoppingService.wsdl#types1"
   <!--Metro -->
   <jaxb:bindings schemaLocation="ShoppingService.wsdl#types?schema1"

Where 1,2,3 in both cases refers to the 1-based count of the xsd:schema
within the single wsdl:type.    The XJC compiler during the wsdl2java
generation process will reject the former for Metro and the latter for CXF.

I'd like this to be standardized so the binding files would be portable
between the two frameworks but I'm not sure which framework is correct. The
CXF method of incrementing the number next to the types seems inaccurate
because there can be only one wsdl:types.  On the other hand, Metro's usage
of the ? as a delimiter does not appear to be defined in the SCD candidate
recommendation (  

Granted, the CXF dev list might not be the most unbiased of forums, but any
idea which team is "wrong"?


View this message in context:
Sent from the cxf-dev mailing list archive at

View raw message