BizTalk Server Orchestration - Map transformation problem and Namespace (BT2004)

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > June 2004 > Map transformation problem and Namespace (BT2004)





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 Map transformation problem and Namespace (BT2004)
Pascal G.

2004-06-20, 11:09 pm

Hi,

Finally, after some fight with BT ;) I managed to "patch" the situation. My
second source comes from a webservice on which I have control. So I put
some attribute declarations to my C# class properties to be serialized as
attributes (instead of elements).

P.G.

"P.G." <none@myserver.com> wrote in message
news:e7AEdN$TEHA.1012@TK2MSFTNGP09.phx.gbl...
> Hi guys, I have a little problem with the generated XSL of a map.
>
> My map is composed of 2 sources and 1 destination. I use an iterator and
> index functoid to get corresponding values from both sources. Everything
> looks fine but the result was not correct.
>
> See 01_Map.jpg for a screen capture of the map.
> See 02_IndexParams.jpg for a screen capture of the index functoid

parameter
> definition.
>
> So what happens is for each vehicle record found in the first source, I

get
> the matching record of the second source (LBSLocation). I consider that
> both source will have the same number of records and will be in the same
> order. So the iterator functoid gives me the index number and the index
> functoid is used to retrieve the "Latitude" based on that index.
>
> But here's the problem, when the orchestraction executes everything is
> created correctly but the latitude attribute of the destination message is
> empty.
>
> So I took a look at the XSLT generated by the "Validate Map". It is
> included as 03_xslt.xml. At some point in the template, a variable named
> "var:v2" is created based on the value returned by the select. Here is a
> part of the select: "[local-name()='Coord' and
> namespace-uri()='http://tempuri.org/'][1]/Latitude/text()". As you can

see
> the Latitude element is not accessed using its namespace. If I modify the
> select that way and I process the xml source manually using a XSL

processor,
> I get the expected result: "[local-name()='Coord' and
> namespace-uri()='http://tempuri.org/'][1]/*[local-name()='Latitude' and
> namespace-uri()='http://tempuri.org/']/text()"
>
> So my question is... is it a bug in BT2004? or am I doing something wrong?
>
> I more info is needed, I can provide source and destination schemas and a
> sample input xml.
>
> thanks.
>
> Sorry for the long post.
>
>
>
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com