I have 3 remarks:
1) I think Contract first is the only valid approach. If both the service consumer and the service providers are in Java, then why using WSDL? Just use the java interface as the contract and use RMI.
2) the WSDL is not the contract, it is part of the contract. The contract might include SLA or special policies applied by the service in this paricular context.
3) Generation of code is fine for the first version of the service interface. But if you think about implementing a second version of the service interface and then a third version, and still keeping a single implementation. Most of the frameworks which are generating code based on the WSDL will be inadequate. The best solution over time will be the one which allow you to configure your mapping between the XML messages and your Value (or Domain) Object models.
For example, a combined Axis/JiBX solution would be perfect or Oracle J2EE App.Server/Toplink OX. Configurable mapping is key if you want your application to support changes over time.
Robin |
java.net RSS Feeds
