cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: Metro vs. CXF difference in enumerating schemas within a WSDL
Date Wed, 14 Jul 2010 21:39:44 GMT

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

Technically, neither.    Nothing in the jax-ws spec that dictates how this is 
supposed to be handled.

Not sure what else to say.   :-(

Maybe something more like:

<jaxb:bindings schemaLocation="ShoppingService.wsdl#types"



On Wednesday 14 July 2010 1:56:55 pm Glen Mazza wrote:
> 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:
> mybindingfile.xjb:
>    <!--CXF -->
>    <jaxb:bindings schemaLocation="ShoppingService.wsdl#types1"
> node="/xs:schema">
>    <!--Metro -->
>    <jaxb:bindings schemaLocation="ShoppingService.wsdl#types?schema1"
> node="/xs:schema">
> 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"?
> Thanks,
> Glen
> [1]
> SD-specified-td1046395.html#a1046395 [2]
> [3]

Daniel Kulp

View raw message