I agree with the two main points of your post. Those are valid points and potential problems of "code first" approach. However, I think these risks can be mitigated (each one is a debate in and of itself, WSDL generation being different and schema usage outside of WSDL) and I think the benefits of using the technology or programming language where your expertise lies outweighs the risks (and not doing so, "contract first" has its own risks which are greater in my experience).
I did not mean to start a big debate here I just do no agree that "contract first" is the better way. Both ways can work and generally *both* rely on some generation step (WSDL into Java stubs or Java into WSDL) which can be problematic. |
java.net RSS Feeds
