BizTalk Server Orchestration - Sending an empty message to a web service

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > September 2005 > Sending an empty message to a web service





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Sending an empty message to a web service
Gary

2005-09-23, 7:49 am

Hi I am trying to send an empty message i.e. no parameters to a web service.
I have created a multi-part messasge type and have tried constructing it
using a construct message and then in the assignment shape using:

XmlDoc.LoadXml("<ns0:GetBatch
xmlns:ns0='urn:xxx.Legacy.Batch.BatchWebService'><ns0:GetBatch
/></ns0:GetBatch>");
GetBatch.parameters = XmlDoc;

and I receive the warning:

Detail: value cannot be null
parameter name: Method Name

I have looked at the article at the following link
http://geekswithblogs.net/cyoung/articles/4634.aspx and tried just using a
construct shape with no assignment but I get compile errors saying that the
message part has not been constructed.

Anybody got any ideas?

Cheers,
Gary
kplkumar@gmail.com

2005-09-26, 5:59 pm

I am not sure. I am try to do something similair. I am publishing an
orchestration as a web service, I need a couple of web methods to just
retrieve data from the database and send me back. So I will not be
passing any arguments when I call this webmethod. In other works, I
need a couple of my orchestration's operations accept empty incoming
messages.

I think it is impossible. But any work arounds???

Gary

2005-09-27, 2:50 am

Hi,

I got my problem sorted yesterday. Basically, I had not correctly named the
operation on my port to the name of the web method that I was calling. I am
not sure what BizTalk does behind the scenes with regards to calling the web
service. I thought by pointing the physical port at the web service and
passing the appropriate message that it would work, but the operation
identifier on the port obviously must play a part.

In your case kplkumar, I guess you can just create a schema of the type of
the incoming message, create a message of the type schema and set it to be
the received message on your receive shape. You will also have to make you
port public I guess.

"kplkumar@gmail.com" wrote:

> I am not sure. I am try to do something similair. I am publishing an
> orchestration as a web service, I need a couple of web methods to just
> retrieve data from the database and send me back. So I will not be
> passing any arguments when I call this webmethod. In other works, I
> need a couple of my orchestration's operations accept empty incoming
> messages.
>
> I think it is impossible. But any work arounds???
>
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com