|
Home > Archive > BizTalk Server General > December 2004 > Soap adapter is caching the responses Help
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 |
Soap adapter is caching the responses Help
|
|
| Dan Meland 2004-12-08, 8:46 pm |
| ok, I make a request to a webservice through the SOAP addapter.
I then take the message from the response, which is correct, and copy
message to one that will be out going.
I change a few fields in the XML, and pass the message back to a different
call to the same webservice through the same, or a different soap adapter
port. (that part doesnt seem t matter.)
Ok here is the problem.
1 the message I am sending to the webservice looks correct when it hits the
send shape. HOWEVER, when i debug the webservice and the message hits, it is
the same message I recieved in the response. I asked for the first time. what
is up.
Any help would be appriciated.
steps:
1. requery the webservice through the SOAP adapter for data,
2. Receive the correct data back in a message,
3. copy the message to a second message.
4. change a few tag values,
5. send the the coppied message back to a different call in the same
webservice through the same or different instance of the soap port.
6. look at the message about to be sent. and copy it to notepad.
7. with the webservice in a debug state, trap the call to the service.
8. copy the XML received in the webservice method,
9. Note, the XML received from the request is the same as the XML sent which
should have been modified.
ok there it is.
Thanks
Dan
| |
| Siva Gowrishetti 2004-12-17, 5:48 pm |
| Dan,
Did you try creating different Message? (using the same web service message
type)
Thanks
Siva
"Dan Meland" wrote:
> ok, I make a request to a webservice through the SOAP addapter.
> I then take the message from the response, which is correct, and copy
> message to one that will be out going.
>
> I change a few fields in the XML, and pass the message back to a different
> call to the same webservice through the same, or a different soap adapter
> port. (that part doesnt seem t matter.)
>
> Ok here is the problem.
>
> 1 the message I am sending to the webservice looks correct when it hits the
> send shape. HOWEVER, when i debug the webservice and the message hits, it is
> the same message I recieved in the response. I asked for the first time. what
> is up.
>
> Any help would be appriciated.
>
> steps:
> 1. requery the webservice through the SOAP adapter for data,
> 2. Receive the correct data back in a message,
> 3. copy the message to a second message.
> 4. change a few tag values,
> 5. send the the coppied message back to a different call in the same
> webservice through the same or different instance of the soap port.
> 6. look at the message about to be sent. and copy it to notepad.
> 7. with the webservice in a debug state, trap the call to the service.
> 8. copy the XML received in the webservice method,
> 9. Note, the XML received from the request is the same as the XML sent which
> should have been modified.
>
> ok there it is.
>
> Thanks
>
> Dan
| |
| Dan Meland 2004-12-30, 7:50 am |
| Ok folks, still have the problem.
I have recreated this in three orchestrations now, and with no resolve.
Any ideas out there?
Dan
"Dan Meland" wrote:
> ok, I make a request to a webservice through the SOAP addapter.
> I then take the message from the response, which is correct, and copy
> message to one that will be out going.
>
> I change a few fields in the XML, and pass the message back to a different
> call to the same webservice through the same, or a different soap adapter
> port. (that part doesnt seem t matter.)
>
> Ok here is the problem.
>
> 1 the message I am sending to the webservice looks correct when it hits the
> send shape. HOWEVER, when i debug the webservice and the message hits, it is
> the same message I recieved in the response. I asked for the first time. what
> is up.
>
> Any help would be appriciated.
>
> steps:
> 1. requery the webservice through the SOAP adapter for data,
> 2. Receive the correct data back in a message,
> 3. copy the message to a second message.
> 4. change a few tag values,
> 5. send the the coppied message back to a different call in the same
> webservice through the same or different instance of the soap port.
> 6. look at the message about to be sent. and copy it to notepad.
> 7. with the webservice in a debug state, trap the call to the service.
> 8. copy the XML received in the webservice method,
> 9. Note, the XML received from the request is the same as the XML sent which
> should have been modified.
>
> ok there it is.
>
> Thanks
>
> Dan
|
|
|
|
|