In order to facilitate a REST architecture for our web service model based VDBs ( see
TEIIDDES-122 ), we need to enable the HTTP binding spec support that WSDL 2.0 provides.
Currently, our web service model generates WSDL 1.1. I would like to keep this behavior
and add an option to the VDB web services tab to optionally generate WSDL 2.0. The WSDL
1.1 would still be generated according to the model definition, but we would convert to
WSDL 2.0 using an Apache project called Woden . The 2.0 version of the wsdl would then be
saved with the VDB. This way there would be no model changes required.
One issue I see here is that we could not re-import the WSDL without modifications to the
importer for the web services model. That has always been something we have strived for in
the past. Granted, we are not claiming support for WSDL 2.0 importing at this time but if
we are generating it, it seems like we should go both ways?
Any thoughts on this approach to WSDL 2.0 generation?