You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by xp...@yahoo.com on 2009/06/24 15:34:05 UTC
CXF - WSDL : Newbie question
Hello group!
I am new to using CXF and have run into initial hiccups. Using JAX-WS styled notations I have deployed my services on tomcat in testing env.
For consumption, I generated local stubs using the published wsdl. The problem is that not all classes are getting generated and some of them are half baked.
What I'd like to ask group here is that - is it a common/professional practice to alter your wsdl manually according to your needs? Or do you make changes elsewhere (in the java stubs themselves)?
I'm unsure as to how to go about this. Any help is appreciated.
Chris
Re: CXF - WSDL : Newbie question
Posted by Andrew Clegg <an...@nervechannel.com>.
2009/6/24 <xp...@yahoo.com>:
> Hello group!
>
> I am new to using CXF and have run into initial hiccups. Using JAX-WS styled notations I have deployed my services on tomcat in testing env.
> For consumption, I generated local stubs using the published wsdl. The problem is that not all classes are getting generated and some of them are half baked.
What exactly are the problems? People here can probably help you iron them out.
> What I'd like to ask group here is that - is it a common/professional practice to alter your wsdl manually according to your needs? Or do you make changes elsewhere (in the java stubs themselves)?
I avoid Java-first for various pretty good reasons [1] but I would
imagine issues in the generated code suggest issues in the WSDL which
in turn suggest issues in the annotations.
It's generally bad practice to alter any generated code isn't it? It
puts a manual step in your build process which will recur whenever you
change the original Java.
Andrew.
[1] http://static.springframework.org/spring-ws/sites/1.5/reference/html/why-contract-first.html
--
:: http://biotext.org.uk/ ::