Any help much appreciated in this regard in terms of sample envelopes you can share or validated WSDL, currently using v28.1 which doesn’t validate in XMLSpy although it seems to work with SOAPUI
Yours,
Adrian
Thanks for the help and the prompt response…and yes 28.1 not v28.1 in the workday snap.
I had crossed my wires, thought you were referring to the URL for the WSDL in the soap snap.
Ok I’ve switched the SOAP snap to use WSSE instead of basic authentication and now I’m getting tenant not available due to patching notification so not good but not bad
On the workday snap front getting the following when pressing the validate button:
failure: Cannot connect to the endpoint reason: Server returned HTTP response code: 500 for URL: https://wd3-impl-services1.workday.com/ccx/service/Arriva3/Integrations/v28.1?wsdl resolution: Please file a defect against the snap
Thought this should be validating against the following instead:
https://wd3-impl-services1.workday.com/ccx/service/Arriva3/v28.1?wsdl
Not sure how …integrations… snuck in.
Ok just checked and the tenant is not being patched and is available through other means, but still getting the following when executing the SOAP Execute using WSSE security:
An exception occurred while executing the SOAP request
Resolution
Verify the input data is correct
Reason
tenant is temporarily unavailable due to server patching
For the workday snap using a workday account I’m getting:
Cannot Parse WSDL
Resolution
Please verify account settings and retry
Reason
Server returned HTTP response code: 500 for URL: https://wd3-impl-services1.workday.com/ccx/service/Arriva3/Absence_Management/v28.1?wsdl
but the url resolves in a browser window - This is a Show Stopper Right Now!.
<?xml version="1.0" encoding="UTF-8"?>-<wsdl:service name=“Absence_ManagementService”>
-<wsdl:port name=“Absence_Management” binding=“wd-wsdl:Absence_ManagementBinding”>
<soapbind:address location=“https://wd3-impl-services1.workday.com/ccx/service/arriva3/Absence_Management/v28.1”/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
OMG - I had a capital 'A’rriva3 in the tenant field arriva3 now validates and I can see the available methods.
case sensitivity aaaargh! - case conversion as feature request please
