| Author |
Get Orchestra to receive a XMLDocument using SOAP
|
|
|
|
How can I make an orchestra exposed a web service that
can receive a XML Domument using soap??
Thanks
Toko
| |
|
| use "Web Service Publish Wizard", it will create the
visual-directory(SOAP) to receive.
| |
|
| Hi
But I cant se how the helps !?
Publishing an Orchestration as a Web Service using the
wizard makes the assumption that callers want to
pass .NET objects that represent their documents instead
of passing the documents directly.
and I need tha client to pass a xmldocument to the
webservice. not using .Net objects
/Toko
| |
| Matt Milner 2005-03-10, 5:54 pm |
| It sounds like what you want is either
a) an HTTP receive where you just post the XML document and don't worry
about having a method signature
b) a generic web service, in which case you can 1) have the message type in
your orchestration be system.xml.xmldocument or 2) modify your generated web
service to accept a string or system.xml.xmldocument instead of complex xml
types.
And, actually, your statement about the web service wizard is a bit
incorrect. The wizard makes it so you can work with the deserialized xml as
..net types (if the message part is a .net type) in your web service, but any
consumer will use the same WSDL that does not specify anything about .Net
types. A Java app could just as easily consume your web service.
Matt
"Toko" <anonymous@discussions.microsoft.com> wrote in message
news:537501c52551$59e6be00$a501280a@phx.gbl...
> Hi
>
> But I cant se how the helps !?
>
> Publishing an Orchestration as a Web Service using the
> wizard makes the assumption that callers want to
> pass .NET objects that represent their documents instead
> of passing the documents directly.
>
> and I need tha client to pass a xmldocument to the
> webservice. not using .Net objects
>
> /Toko
| |
|
| Thanx Matt
>-----Original Message-----
>It sounds like what you want is either
>a) an HTTP receive where you just post the XML document
and don't worry
>about having a method signature
>b) a generic web service, in which case you can 1) have
the message type in
>your orchestration be system.xml.xmldocument or 2)
modify your generated web
>service to accept a string or system.xml.xmldocument
instead of complex xml
>types.
>
>And, actually, your statement about the web service
wizard is a bit
>incorrect. The wizard makes it so you can work with the
deserialized xml as
>..net types (if the message part is a .net type) in your
web service, but any
>consumer will use the same WSDL that does not specify
anything about .Net
>types. A Java app could just as easily consume your web
service.
>
>Matt
>
>
>"Toko" <anonymous@discussions.microsoft.com> wrote in
message
>news:537501c52551$59e6be00$a501280a@phx.gbl...
instead[vbcol=seagreen]
>
>
>.
>
|
|
|
|