We are trying to design a generic webService endpoint that will be invoked for different message types of different structures from a SharePoint portal. So we can’t define a particular message as input of this service.
We are trying to use $xmldata as input. Upon receiving the message, we will extract the key details and process further.
Is there any better approach to create a generic webService?
What you want is a Do-Anything WS, so an “input” and an “output” parameter will work.
you basically can define your input and output separately, and modify it as you will.
But this will be, to certain extant, defeating the idea of web service, which ideally should let the client system clearly know what the services are, and what parameter should be passed on.