cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Diephouse" <>
Subject Re: contract first using either XSD or XML plus Trang
Date Fri, 04 May 2007 10:34:32 GMT
I think (b) is really important. It allows you to do schema first
development without the bulls*t of the WSDL. Once you get that working, its
real easy to support (a).

FWIW, (b) is already somewhat possible. XSD->JAXB. Then you can write your
service interface using JAXB beans. CXF should then generate the WSDL for
you. (Although this will probably lose the original schema documentation,
since JAXB will regenerate the schema. We need a way to supply just

- Dan

On 5/2/07, James Strachan <> wrote:
> Writing WSDL by hand is a bit sucky. I enjoyed Craig's recent post...
> I wondered if anyone had ever looked at creating some contract-first
> tooling which was like this...
> a)  example XML documents -> XSD
> b) XSD with naming conventions/annotations -> WSDL
> c) WSDL to Java (as we currently have)
> i.e. so folks could start at a, b or c rather than just forcing folks
> to write WSDL.
> e.g. it'd be cool to extend the maven tooling so you could just list
> the example XML documents to use to create the XSD to create the WSDL
> to create the Java contracts :)
> On the home page it seems to kinda say there's code generation for XSD
> to WSDL, but I've not spotted any examples yet. Is this true? I've
> seen the XSD to Java (which seems to be like the JAXB2 XSD to Java
> stuff). I was wondering if folks had looked at doing XSD to WSDL and
> using trang to add example-XML to XSD etc?
> --
> James
> -------

Dan Diephouse
Envoi Solutions |

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message