| Chris Holliday 2004-03-06, 11:35 am |
| <this is cross posted to the Biztalk beta newsgroup>
The plot thickens.
Brief overview:
- Receive shape picks up a message from a folder
- Delay shape waits 24 hours
- Construct message shape
- Message assignment shape builds the string to be passed to a
webservice (parameter is called "params")
- String is built from distinguished properties in the message first
picked up by the receive shape
- Send shape sends said message
- Receive shape is supposed to receive the response from the webservice.
- .... a bunch of other stuff that we aren't getting to yet
To reiterate a previous notion: this used to work in the BETA.
The orchestration is failing on the second receive shape with the following
error:
"Required part params was not found in the message"
This seems out of place. Why would the "params" value come into play in the
response? I have many other orchestrations that are working fine. They are
using different patterns, none of which are expecting a real message back
from a webservice. For example, I complete some orchestrations by passing a
message to a webservice and just getting a simple string acknowledgement
back. This orch is expecting a real message.
I have saved all messages from the orch and the string that is supposed to
go to the webservice is correct.
I have rebuilt the orchestration from the ground up. I have tried with
different webservices. I have used different patterns (build a message that
will be used as the string as opposed to concatenating distinguished values
to the string). Nothing gets me any kind of different response. Could this
be some kind of obtuse permissions issue? I can't even really figure out a
good way to debug this. I have tested the webservice using HTTP GET to pass
in the identical string and of course it works.
Is anyone having success passing a constructed message of any variety to a
webservice and getting a useful response back?
Losing hair fast... help!!!!
Chris
|