Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
6 subscribers
Views
2432 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
My team is working with getting the WS Smart Service to connect and work with th
robbier
over 9 years ago
My team is working with getting the WS Smart Service to connect and work with the Docusign web service API. It seems we can get a SoapUI client to successfully make calls to the service and get the document information based on request.
With the smart service the problem seems to be, even though the WSDL url is
demo.docusign.net/.../dsapi.wsdl
, the namesspace associated with it is
www.docusign.net/.../3.0
(so http not https). So notice the difference here--actual WSDL is https but the namespace is http.
We can update the SoapUI config to accomodate but it seems the that the WS Smart Service always uses the default namespace which results in an http 301 error. Is there anyway to override this in the smart service?
OriginalPostID-188467
OriginalPostID-188467
Discussion posts and replies are publicly visible
Parents
0
robbier
over 9 years ago
I was looking at the Advanced Web Service Plug-In. It didn't give details in the description as to whether it allowed overriding but I'll download and give it a try.
Thanks for your suggestions!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
robbier
over 9 years ago
I was looking at the Advanced Web Service Plug-In. It didn't give details in the description as to whether it allowed overriding but I'll download and give it a try.
Thanks for your suggestions!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data