parse incoming SOAP message.

[Sai]

Friends,

Any body know how to parse incoming SOAP message.
Do I have to create web-services to do this. I know nothing about how
to do it.
Any direction to start would be great.

Thanks,
K

 

[Guest]

You don't neccesarilly need to use the built in functions to create a web
servive, you can parse the SOAP message yourself in a regular aspx page. It's
just XML.

 

[Joerg Jooss]

Thus wrote Guffa,

You don't neccesarilly need to use the built in functions to create a
web servive, you can parse the SOAP message yourself in a regular aspx
page. It's just XML.

It's an utter waste of time. wsdl.exe will create a web service proxy for
any old Web service that exposes a WSDL.

Cheers,

 

[Guest]

It's an utter waste of time. wsdl.exe will create a web service proxy for

any old Web service that exposes a WSDL.

Yes, for any web service with a static dfefinition.

A while back I needed to make a web service that returned different fields
depending on a number of definitions in a database. It's not practicaly
possiblel to create a proxy for every definition.

 

[Joerg Jooss]

Thus wrote Guffa,

Yes, for any web service with a static dfefinition.

A while back I needed to make a web service that returned different
fields depending on a number of definitions in a database. It's not
practicaly possiblel to create a proxy for every definition.

That depends on the number of proxies and effort required to manually code
them. But that equation can certainly work out in favor for manual coding.

Cheers,

 

[Tarun Mistry]

I have recently been in the same position, the way i see it, SOAP can be
used for RPC or to transmit XML payloads between systems.

In the case of RPC, you have a standard web serivce, not very complicatated,
when you want to send payloads things become more difficult. I manually
accepted the incoming HTTP post, and converted to an XmlDocument and
processed accordingly. Is there a better way? Please explain the proxy
component.

Thanks,
Taz

 

[Joerg Jooss]

Thus wrote Tarun,

I have recently been in the same position, the way i see it, SOAP can
be used for RPC or to transmit XML payloads between systems.

In the case of RPC, you have a standard web serivce, not very
complicatated, when you want to send payloads things become more
difficult. I manually accepted the incoming HTTP post, and converted
to an XmlDocument and processed accordingly. Is there a better way?

Both SOAP RPC and Document/Literal are first class citizens in the .NET framework.
If you're dealing with POX (Plain Old XML), you're sort of on your own without
WCF.

Please explain the proxy component.

Check out the documentation of wsdl.exe in the .NET SDK documentation at
http://tinyurl.com/3f3cn.

Cheers,