It seems Remedy does not interperet the WSDL file the same way most of the xml/soap tools do. If anyone has any experience/success merging or flattening WSDL and multiple XSD file any advice would be appreciated.
I am currently working on a web service integration with UPS, they do provide shipping api's. I have created WSDLs that I can successfully submit to UPS and get valid returns with cost, tracking # and label (in base64 text string) which I can decode and display the label in a view field, and I can create a hyperlink for tracking in my Remedy form. There is s 2 step process Shipconfirm and ShipAccept (submit data > get rate returned > Accept proposed rate) , and a single step ProcessShipment. You can find their resources here: https://www.ups.com/upsdeveloperkit/downloadresource?loc=en_US We had to use a WSDL:merge utility to combine the base WSDL and associated xsd files into a single WSDL file. My issue is that all this works when testing with SOAP UI. When I load the WSDL in Remedy web service, I can map my input fields to the appropriate elements and submit, but Remedy does not load the WSDL with the proper namespaces within the WSDL, the header section is displayed but there is no body tag and UPS rejects the submission with 'error client data' or 'xml not well formed' Thanks in advance, Bob _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
