Of course all web service developers do not use Java? Those that have competencies in other areas should use those areas to develop, similarly. The Java EE 5 annotation support allows you to be quite specific in Java code (as you can be starting from the WSDL, and if you are a java developer (as I stated) then it makes much more sense to rely on your expertise.
And of course the WSDL is how you agree upon uniformity across the enterprise? However that has nothing to do with how you implement the service. The interoperability of the service, and the point of services in general, is the "agnostic" standards based description of the service and protocol (SOAP/Schema/WSDL). The resulting WSDL will not be different if you start from code than if you start from the WSDL itself? If it were then *that* might be a valid point to start from contract. (Saying WSDL is the "business perspective" agreed upon interface is not a reason, that is obviously the goal either way.)
I understand your statement that your intention in the article was to demonstrate Axis2 capabilities, and I respect that, the article does that well. But the article also itself debates the code first versus contract first approaches so a response in that arena should not be completely unexpected.
The more extensible and enterprise friendly way is to use what suits your organization better, if you are Java competent that is likely Java. The end result which will be exposed to the "enterprise" will be implementation agnostic and users/clients will have no idea what language is even involved. |
java.net RSS Feeds
