cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Kulp <>
Subject Re: CXF changes the WSDL
Date Mon, 03 Oct 2011 01:22:03 GMT

Any chance you could file a test case?   We do have some tests to make sure 
the annotations and stuff are preserved.  However, they may be for external 
xsd's, not schemas embedded in the wsdl.   I'd have to dig in more to check 
that, but a test case would be great.


On Saturday, October 01, 2011 10:08:42 AM Bengt Rodehav wrote:
> Hello,
> We're using CXF 2.4.2 to provide a web service API to a legacy application.
> We are in the process of increasing the quality of the API in a number of
> ways.
> First, we are typing the interface more strictly. E g instead of specifying
> that a value is a string, we say that it's exactly one character long and
> also enumerate it's valid values. We also try to add documentation to the
> WSDL. The following is a typical case:
> <xs:simpleType name="MyType">
> <xs:annotation>
>  <xs:documentation>
> A = ...
> B = ...
>  C = ...
> </xs:documentation>
> </xs:annotation>
>  <xs:restriction base="xs:string">
> <xs:pattern value="A|B|C" />
>  </xs:restriction>
> </xs:simpleType>
> However, even if we feed the above WSDL to CXF (we use WSDL first), in
> runtime when asking for the WSDL (using ...?wsdl), the above information is
> gone. The type is simply a string and the documentation is gone.
> Why is this? Is it a bug? What is best practice regarding strict interfaces
> and documentation using CXF?
> /Bengt
Daniel Kulp
Talend -

View raw message