How to map data from 2 nodes in Input into one node on output

How to map data from 2 nodes in Input into one node on output

Post by tatyana » Thu, 13 May 2004 06:55:24


I replied you at the other thread (under tools).


--------------------
microsoft.public.biztalk.appintegration,microsoft.public.biztalk.general,microsoft.public.biztalk.orchestration,microsoft.public.biztalk.sdk,microsoft.public.biztalk.server,m
icrosoft.public.biztalk.xmltools
microsoft.public.biztalk.appintegration,microsoft.public.biztalk.general,microsoft.public.biztalk.orchestration,microsoft.public.biztalk.sdk,microsoft.public.biztalk.server,m
icrosoft.public.biztalk.xmltools
microsoft.public.biztalk.server:9418 microsoft.public.biztalk.appintegration:6641
two separate instances instead of just one. I have tried using all combinations of the functoids (looping or value mapping flattening, straight copy, etc) but still get the
same results. See below for details:



Here is the Input schema (address distributed over two nodes)



<Record E><Address 1>1366 Street</Address 1></Record E><Record F><City> Chicago</City><State>IL</State><ZIP>60606</ZIP></Record F>



Here is the output schema (address supposed to be in one node)



<Acccount Contact><Address 1></Address 1><City></City><State></State><ZIP></ZIP></Acccount Contact>





Problem- Output looks like this (address distributed over two nodes instead of one):





<Acccount Contact><Address 1>1366 DEVON</Address 1><City></City><State></State><ZIP></ZIP></Acccount Contact><Acccount Contact><Address 1></Address
1><City> CHICAGO</City><State>IL</State><ZIP>60606</ZIP></Acccount Contact>


--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.yqcomputer.com/

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
 
 

1. [RFC][PATCH] ia64 node hotplug -- cpu - node relationship fix [2/2] cpu-to-node map

2. [BUGFIX][PATCH] cpu to node relationship fixup take2 [2/2] map cpu to node

AMEZAWA Hiroyuki wrote:
This patch failed to compile in my IA64 box, my machine is not NUMA machine,
there is unmap_cpu_from_node not defined error like this.

arch/ia64/kernel/built-in.o: In function `arch_unregister_cpu':
arch/ia64/kernel/topology.c:52: undefined reference to `unmap_cpu_from_node'
make: *** [.tmp_vmlinux1] Error 1

thanks
bibo,mao

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

3. [patch -mm 4/7] x86_64: map fake nodes to real nodes

4. How to set the node indent property between the parent node and the leaf node

5. xsl variable $node/text() but $node can non-node-set help!

6. Cluster node failover takes very long only from Node A to Node B

7. [patch -mm 5/7] x86_64: map fake nodes to real nodes

8. Cluster node failover takes very long only from Node A to Node

9. [ciao-users] Relationship cardinality between Node Manager, Node App Manager and Node App

10. [BUGFIX][PATCH] cpu to node relationship fixup take2 [2/2] map cpu to node

11. node-node adjacency matrix to a node-arc adjacency matrix

12. select nodes with child node A and child node B

13. Selecting Node based on parent Node attrib and sibling Node value

14. [RFC][PATCH] ia64 node hotplug -- cpu - node relationship fix [1/2] empty node fix

15. + fix-cpu-to-node-relationship-fixup-map-cpu-to-node.patch added to -mm tree