Stay with starting from schemas and WSDL. What youre describing as
contract first
is really the Document Based Web services pattern
http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns/
http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns2/
http://java.sun.com/developer/technicalArticles/xml/jaxrpcpatterns3/
/s
Vijesh A.V. wrote:
>Hi all,
>
>Comparing Contract-First and Code-First approach in developing web
>services, I find the former is much better in terms of clarity and the
>quality of generated source and the interoperability issues. The
>generated artefacts are much more predictable.
>
>What is the general feeling among the community?
>
>I used JAX-WS 2.1 RI for Contract-First approach and it worked
>beautifully. This being non portable makes it less attractive. BTW, can
>I use this in production environment? If so, how much/what changes
>should I have to do to make it portable later?
>
>I understand that portable JAX-WS can be developed/deployed in
>Glassfish. But it seems to be in favour of Code-First approach.
>
>Probably a foolish attempt:
>The same war created from JAX-WS RI is deployed in Glassfish after
>removing sun-jaxw.xml and web.xml (don't know this is a proper way, just
>an attempt). The server is not recognising the included wsdl, instead it
>is looking for one with the name MyClassImplService.wsdl (MyClassImpl
>being the endpoint implementation) !!!. I.e. as if the deployed war for
>code-first approach!!!
>
>What could've went wrong?
>
>Also I don't find any example/article about using contract-first
>approach in glassfish. I have a feeling that contract-first (top down)
>is not recommended in EE5 (or at least in Glassfish).
>
>May be I lack proper R&D on developing portable JAX-WS using Glassfish.
>Any helpful guidance would be highly appreciated.
>
>Best Regards,
>Vijesh
>
>