CODEWITHSUNDEEP
asp.netservicestack
Stephen Patten
Stephen Patten

Reputation: 6363

How migrate existing SOAP endpoints to ServiceStack

I've the good fortune of being able to kick off a new project with the tooling of my choice, which is ServiceStack. The Architecture is very solid and the product was out before web api was even a glimmer in someones eyes. That being said, it would be a great plus, if I could also recreate some legacy SOAP endpoints and route then through this service instead of have two apis running at the same time. Is there a preferred way to do such a thing?

Thank you, Stephen

Upvotes: 2

Views: 220

Answers (1)

mythz
mythz

Reputation: 143359

Not sure about what migrating legacy SOAP endpoints over to ServiceStack entails.

But ServiceStack's SOAP support works like all the other REST, Web and MQ endpoints and Content-Types, where it automatically exposes SOAP endpoints around your services Request and Response DTOs allowing it to be called via SOAP 1.1/1.2.

The inherent limitation in SOAP means that only Services that support POST (i.e. Post() or Any()) are available to be called by SOAP. For services that use any other HTTP/REST Verbs it will be disabled in the metadata pages as seen in the SocialBootstrap API metdata pages. See SOAP Limitations for other things you should be weary of.

The metadata pages also contain links to your services WSDLs and XSDs, e.g:

If you want to host legacy .asmx SOAP services in the same application than you should host ServiceStack on a /custompath so you're able to use it with any other ASP.NET Web, MVC or other web services frameowrk.

Upvotes: 2

Related Questions