On 10/24/2011 11:02 AM, Michael wrote:
...
I understand your comment about the "Java first" approach. However, IMHO
whether you do "Java first" or "WSDL first" there are still two entities you
need to keep sync'd up, the WSDL and the Java code. So if you change the
code you need to regen the WSDL and if you change the WSDL you need to regen
the code!
My point is that you should first create the WSDL using any technique
you like and the WSDL should then become the definition of the service
interface. If you later change the WSDL, you need to regenerate both
client and service code to work with the new interface.
I'd suggest that the approach of generating WSDL from Java code
on-the-fly is far more likely to create problems with broken linkages,
and this outweighs the minor advantage of not having to do service code
generation.
- Dennis
