I want to get the request/response from the WCF consuming client as soap envelope. Is there any way to get it by adding the service reference in any of the c# application?.
If you have added your service reference and want to capture the actual SOAP message info you can do this:
You can use an message inspector and capture the SOAP message requests and responses:
more info here
or you can use system.diagnostics to log the information (not good for production usage, only for debuggin):
message logging
Related
I am using service that can only send messages using webhook. The only thing I can set up in that webhook are HTTP endpoint, user name and password (you can see it on the screenshot below). I would like to send messages to my event hub, but I don't know how to find its HTTP endpoint. The only thing I could find was SAS Endpoint.
Event Hubs offers a REST API that allows you to perform a subset of the operations supported by its AMQP API. Publishing basic events via REST is possible and would use the endpoint: https://{servicebusNamespace}.servicebus.windows.net/{eventHubPath}/messages.
The full set of documentation for the REST API can be found here, and the specifics for sending events here.
I am not able to parse docusign envelope status notification and could not find anything to do so. Is there anything already in place in library?
Here is one that uses AWS - https://github.com/docusign/connect-csharp-worker-aws
It's not a "sample app" but more of code example, and it assumes that you have a worker separately (so not getting the messages directly on your server).
The listener code is here (https://github.com/docusign/connect-node-listener-aws)
DocuSign Connect Guide states that when creating a listener, for the method name DocuSignConnectUpdate, you need one parameter type DocuSignEnvelopeInformation.
Only problem is on their DocuSign.eSign namespace, there is no DocuSignEnvelopeInformation class to be found.
Is the guide out of date or am I missing something?
The part of the Connect Guide you're quoting only applies if you configure your webhook (Connect) subscription to use SOAP message transmission format. (Which I advise against.)
If you choose to use SOAP message transmission format, your listener needs to be a SOAP server that will process incoming SOAP requests to method DocuSignConnectUpdate with parameter DocuSignEnvelopeInformation
In this case, your app is receiving the SOAP requests, not requesting them, as is more usual when using SOAP. Because your listener is receiving the SOAP requests to DocuSignConnectUpdate, it does not appear in the DocuSign Signature SOAP WSDL file that you reference. That WSDL file and name space describe the methods that your app requests.
Rather than setting up a SOAP listener, it is usually easier to set up a plain HTTPS listener (server) to receive and process the incoming webhook messages.
I want to implement event notification webhook method into my app. I am using docusign-java-client SDK for docusign, but I am unable to find any example using SDK. Can anyone provide some example to achieve this?
I'm sorry to report that we (DocuSign) don't yet have a Java recipe for this. We do have a Python example. Java is on the list of things to do. Perhaps someone else can provide an example in the meantime.
Here is a general description:
First, set up your webhook subscription. You can have an envelope-specific webhook subscription by including the eventNotification fields in your envelope create request.
Or you can set up a more general subscription by using the "Connect" feature. You can setup Connect subscriptions either via the DocuSign web tool, or programmatically.
As part of the subscription you provide your url for the incoming XML notification messages.
To handle them, you write a small web app using whatever web app framework is easiest for you and your stack. Your web server will receive the incoming https calls from DocuSign.
You can see what the incoming XML messages look like by using the beta Recipe Framework. Run it on Heroku. Use the embedded signing recipe and click the button to see the Webhook / Connect messages. You can then see the sorts of messages that you will receive.
Your incoming message web server will simply parse the XML messages and then handle them accordingly.
Thanks for using the webhook system. Please ask more questions here if you have any issues.
I'm using ServiceStack to develop an SOAP service, and i want to customize my soap service operations soapAction (e.g.: soapAction="http://mydomain.org/operationName"), how can i achieve this ?
I've already read the documentation # service stack's github wiki.
ServiceStack support of SOAP basically comes down to embedding the services Response DTO inside a standard SOAP message. This allows existing services to be accessible via SOAP without any consideration for SOAP itself.
Any additional support of SOAP features need to be opt-in and can be added via pull-request. The SoapHandler.cs class is the class that prepares the SOAP response message.