Currently I have the need to expose my tuxedo Service in a pre-created WSDL file (with all the fields names and namespaces already defined). Searching the web and the examples presented in the Tuxedo and Salt Package, I was able to configure most of the fields but still can't remove the wrapper inbuf tag.
Is there any parameter or configuration I can use to eliminate this tag so I can expose the SALT generated WSDL the way I want? Or is it a requirement for every tuxedo service to have his input exposed that way by using SALT?
If you need anything else in order to provide an answer for this, please let me know. I'm also open to any sugestions.
Thanks in advance,
We don't really support using an existing WSDL file to access an existing Tuxedo service. This is not part of our design goal. Is there a reason you need to use an existing WSDL and not the WSDL file generated by SALT? In the general case, this could be extremely difficult if not impossible for us to support as the shape of the message as defined in the user provided WSDL may not come close to matching the shape of the message required by the Tuxedo service.
Oracle Tuxedo Chief Architect
Hey Todd, thanks for your reply,
I understood your points on not supporting an existing WSDL to define the SALT service. So, there's no way for me to remove the <inbuf> and <outbuf> tags from the tuxedo generated WSDL? Those ones are needed to support the SALT -> Tuxedo Service communication?
Once again, thanks,
I've tried your suggestion above. I've set the env variable as shown bellow:
Recompiled my server, repository, tuxconfig and saltconfig and started up Tuxedo again. But, even so, I've still have the inbuf tag on the newly generated WSDL:
<xsd:element name="inbuf" type="tuxtype:fml32_tuxService_In"/>
Did I do something wrong in my configuration? I'm using SALT package salt12110_64_linux_5_86.bin and Tuxedo tuxedo12110_64_linux_5_x86.bin.
Thanks for your support and for helping me on this,