Hi, I'm wondering whether there is a way to "enforce" the contract-first approach using CXF.
The reason I'm asking is that I created a web service following the contract-first approach but forgot to specify the "wsdlLocation" attribute within the endpoint's configuration. The CXF runtime then recreated a WSDL and XSD's for the published service (which naturally lacked details of the original files such as restrictions in type definitions etc.) from the generated Java types. It took me quite a while to notice that the published artifacts weren't the original ones. So instead of falling back implicitly to the code-first approach I think it would be great if there was an option such as "enforce implementation style". Setting this option to "contract first" would cause the runtime to fail starting up in such cases with a meaningful message describing the wrong/missing configuration. Is there something like that possible with CXF? Thanks, Gunnar
