S
Shaji Sethu
Hi,
I have been investigating the use of OTA specification for developing
web services (http://www.opentravel.org). These schemas were developed
primarily for Travel Industry and cover all facets from airlines to
hotels. At the outset OTA decided to support ebXML instead of WSDL and
WS-I. Now I can retrofit OTA schemas into WSDL to make it work. The
problem is that the schemas are quite convoluted and has multiple
includes and strange referencing and every time I run WSDL.EXE it falls
over with errors. My wsdl as such is fine as i verified it using XML Spy 5.
I just wanted to know if anyone has had a successful development
experience with OTA messages on .NET platform, if so how they went about it.
Any help is appreciated.
Regards
Shaji Sethu
I have been investigating the use of OTA specification for developing
web services (http://www.opentravel.org). These schemas were developed
primarily for Travel Industry and cover all facets from airlines to
hotels. At the outset OTA decided to support ebXML instead of WSDL and
WS-I. Now I can retrofit OTA schemas into WSDL to make it work. The
problem is that the schemas are quite convoluted and has multiple
includes and strange referencing and every time I run WSDL.EXE it falls
over with errors. My wsdl as such is fine as i verified it using XML Spy 5.
I just wanted to know if anyone has had a successful development
experience with OTA messages on .NET platform, if so how they went about it.
Any help is appreciated.
Regards
Shaji Sethu