I'm looking for open source solutions for WSDL protocol conversion.
This is where you'd have a WSDL web service interface on one side, a WSDL web service interface on the other and then a flexible field mapping (and possibly a sequence definition between operations) between the two.
It seems to be a standard pattern, or requirement, as business solution to provide something like this without needing to create code for each WSDL then use a developer to create the links between them.
Extending the mapping protocol with parameter lookups in a database and possible other small processing hooks.
For example I'd take protocolA.wsdl, protocolB.wsdl, a mapping meta-language definition and then just push the button.
Currently the place I'm at uses Java, implements a WSDL by code generating it then implementing java to connect them (using Apache based tools). The problem is that development is outsourced and I'd like to get a grip by productising the protocol conversions - having an example of how this could be done would resolve the impending war..
This is where you'd have a WSDL web service interface on one side, a WSDL web service interface on the other and then a flexible field mapping (and possibly a sequence definition between operations) between the two.
It seems to be a standard pattern, or requirement, as business solution to provide something like this without needing to create code for each WSDL then use a developer to create the links between them.
Extending the mapping protocol with parameter lookups in a database and possible other small processing hooks.
For example I'd take protocolA.wsdl, protocolB.wsdl, a mapping meta-language definition and then just push the button.
Currently the place I'm at uses Java, implements a WSDL by code generating it then implementing java to connect them (using Apache based tools). The problem is that development is outsourced and I'd like to get a grip by productising the protocol conversions - having an example of how this could be done would resolve the impending war..