Re: Mapping Response On Request/Response Port
- From: "Wor Tony" <anthony@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 27 May 2007 17:31:43 GMT
"Wor Tony" <anthony@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AEh6i.4403$zL6.3665@xxxxxxxxxxxxxxxxxxxxxxx
Can anyone help with this:Replying to my own question - I've found the problem! I wished I'd posted
Biztalk 2004 SP2
Windows XP SP2
I have created 2 schemas (1 for the input message and 1 for the outpt
message). Namespaces are along the lines of http://schema/req and
http://schema/rsp.
I've published these schema files as a web service.
I've created an orchestration with a request/response port receiving and
sending an xml dcoument.
I'm successfully transforming the request on the receive port and my
orchestration does it's thing and returns a message of type xml document
containing the required response (along with the correct response
namespace).
I don't want to transform the response as it's already in the correct
format so I have not specified a map. All appears to be well up to this
point, however, when my web service gets the response back from BTS it is
an empty "type" that is returned i.e. the invokeResponse[0] variable
contains my type but there is no sttructure/data below this. I've tried
this with both xml and passthrough send pipeline with no luck. I've tried
mapping on the send also to no avail. Does anyone know why this is
happening?
Thanks.
this 2 days earlier it would have saved me 2 of the most annoying, most
frustrating days of my life - and this is a bank holiday weekend when I
shouldbe having fun!.
Anyway, the problem was due to the response being returned in my orch:
The failing response was:
<Output
xmlns="http://schemas.uk.experian.com/experian/wbsv/msg/screenless1/v100"><Response><Person><Name>A
B</Name></Person><Address><Formatted>The house
etc.</Formatted></Address></Response></Output>
whilst the one that works is:
<ns0:Output
xmlns:ns0="http://schemas.uk.experian.com/experian/wbsv/msg/screenless1/v100"><Response><Person><Name>A
B</Name></Person><Address><Formatted>The house
etc.</Formatted></Address></Response></ns0:Output>
See the subtle difference? the ns0 prefix. I'd fallen foul of the default
namespace issue. I've read about this all weekend and never realised that
it was affecting me. Anyway, thanks for listening, onto the next problem
:-)
AP
.
- References:
- Mapping Response On Request/Response Port
- From: Wor Tony
- Mapping Response On Request/Response Port
- Prev by Date: Mapping Response On Request/Response Port
- Next by Date: Re: The transport proxy method DeleteMessage() failed for adapter
- Previous by thread: Mapping Response On Request/Response Port
- Index(es):
Relevant Pages
|