Finding out the mapper can do what I want it to do
This is a follow up post to my previous post talking about how I used some XSLT with an interim schema to get some mapping done. In my travels around the internet since then I have found a post from Jeff Lynch about how to use the mapper to map “Small Loops“. Well this was exactly what I was trying to get done in my previous post. Simply put the looping functoid can get done what I need. No more interim schema!
here is the new and improved map
Notice how I linked the PONum, ShippingDate attributes to the Looping functoid seperately from the Item element. Once I slowed down long enough to think about what the XSLT this would generate it made sense. Each element or attribute plugged into the left side of the Looping functoid will have it’s own loop created for it. That is the key here. I have also updated the source code for this guy.
I have to say, I like this solution much better!
1 Comment »
Leave a comment
-
Recent
- What I Learned Yesterday 12
- What I Learned Yesterday 11
- What I Learned Yesterday 10
- What I Learned Yesterday 9
- Energy Options for the US
- What I Learned Yesterday 8
- What I Learned Yesterday 7
- What I Learned Yesterday 6
- Finding out the mapper can do what I want it to do
- Some XSLT for when you just can’t get the mapper to do what you want it to do
- What I learned yesterday 5
- What I Learned Yesterday 4
-
Links
-
Archives
- May 2008 (2)
- April 2008 (2)
- March 2008 (3)
- February 2008 (3)
- January 2008 (5)
-
Categories
-
RSS
Entries RSS
Comments RSS
[...] spot to put stuff he does not want to forget « What I learned yesterday 5 Finding out the mapper can do what I want it to do [...]
Pingback by Some XSLT for when you just can’t get the mapper to do what you want it to do « Ben Runchey’s Integration Dev Blog | February 19, 2008