Hi all,
I was researching about publishing processes as web services in Appian and the use of WSDL, and I would like to know if there are any limitations in the definition of XSD types. In a schema defined in the WSDL, can one schema reference another schema within the same WSDL? Are there limitations with the data types?
Thanks!
Discussion posts and replies are publicly visible
Publishing model via SOAP is considered legacy, but still somewhat supported via the admin console. I recommend to not go that way.
Did you consider to implement a normal Web API that accepts XML instead of JSON?
Hi Stefan,
Yes, I know what you mean. My doubt is merely based on expanding knowledge in case I have to work with WSDL.
I wrote the post in case someone could resolve my doubt. When the time comes, I would implement a web API that invokes the process, as you well suggest.Thank you!
Not sure about WSDL. In my experience everybody avoids using it. I consider this not be a hot topic in the future.
But, as WSDL is not specific to Appian, I suggest to check other resources.
I'll do that.Thanks for your time!
Could you explain a little bit more about what you want to achieve? Publishing a model as a SOAP web service is not a problem, because the generation of the wsdl is handled by appian.,
This is different if you want to consume SOAP Services (HTTP/SOAP or EMS/SOAP), because you are no the owner or generator of the wsdl , and that means that you don't have control over the schemas included... and that can be a problem.
Okay, so if we wanted to use the 'call web service' smart service to consume a SOAP service, we might have some problems.
Reading the smart service Appian documentation, I see the following limitation:
WSDLs that utilize data types containing the following XSD constructs return an error if you attempt to to configure specific operations that use them.
But I'm not sure if I understand what it refers to. I don't know if you could give me an example.
The SOAP support in Appian is very basic, while SOAP became a bloody mess of a standard over time.
As I try to avoid SOAP, I do not have any examples at hand, but I am sure the internet has all the info you are looking for.
That means that if you have a SOAP service , and need to generate your datatypes from the schemas included in the WSDL, you will probably have problems with the generation (if uses union, choice or mixed contents in the wsdl, or if you have more than 3 levels of nested schemas)
Anyway, you may generate your request with no datatypes, but that means that you will have to generate your request by hand, and won't have the validation when sending the message (but wil be made in the server)
On the other hand, not many wsdls contain this structure, and you can always modify the schemas by hand
When you say "implement a normal Web API that accepts XML", do you mean setting up a header in the Web API object as follows?
When using SOAP services the body of the request is an XML. You also have soap headers, but that is different. These are values that are informed in the header of the message and contains information about it , for example, the content type of the message..
I think that What Stephan suggests ,is to expose your service via web api accepting xml rather than json.