http://blog.gerd-saurer.com/2008/01/06/annotations-java-web-service-developer-pack/ Fri, 22 Jul 2011 13:43:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://blog.gerd-saurer.com/2008/01/06/annotations-java-web-service-developer-pack/comment-page-1/#comment-97 Rupert Meindl Sun, 06 Jan 2008 11:32:23 +0000 http://blog.gerd-saurer.com/2008/01/06/annotations-java-web-service-developer-pack/#comment-97 For me the style seems not so alien. Because of the nature of WSDL you have to define a mapping between the service definition and the concrete implementation. Annotations on the parameter level make sense because they bind one side of the mapping so it is not so error prone as if you use strings. And if it is formatted nicely, you can read it ;-). In the second part I do not understand the problem: if I build up a client for an WSDL defined interface my implementation will always use the information exposed by the interface description and it does not matter how the service is implemented at all. For me the style seems not so alien. Because of the nature of WSDL you have to define a mapping between the service definition and the concrete implementation. Annotations on the parameter level make sense because they bind one side of the mapping so it is not so error prone as if you use strings. And if it is formatted nicely, you can read it .
In the second part I do not understand the problem: if I build up a client for an WSDL defined interface my implementation will always use the information exposed by the interface description and it does not matter how the service is implemented at all.

]]>