Hi Michael,
WSDL first as well as java first is possible. Take a look at the
wsdl_first example in the distro. In this example the code for the
service interface and data classes is generated but the config in spring
then only uses the generated classes to build the service. So the same
config works if you code the classes by hand. You only will have to make
sure to set the necessary JAX-WS and JAXB annotations. I think mainly
the @Webservice annotation is mandatory.
If you do java first because you only want remoting between your own
client and server then you may also want to look at the spring
HttpInvoker and HttpExporter and this way avoid
soap alltogether. If on the other hand you want to achieve loose
coupling then you should rather go contract first. Some time ago I wrote
an article how to create contract first style wsdls from java code:
http://www.liquid-reality.de/display/liquid/2008/08/20/Defining+Contract+first+webservices+by+generating+wsdl+from+java
Christian
Am 21.02.2011 17:33, schrieb Michael:
I just picked up a copy of Spring In Action. In some CXF documentation I have
noticed that CXF uses Spring. Can someone provide a quick over view of how CXF
uses Spring?
More specifically, after quickly scanning the Spring In Action Table of Contents I noticed that the only web
services chapter was "Building contract first web services in Spring". I'm not sure what that
means for those who would like to build Java first web services, but does the CXF support for Spring allow
both "contract first" and "Java first" web service implementations?
Thanks.
--
----
http://www.liquid-reality.de
