Drawing images gives 2 different results with the same code.

Question

Im adding my code on here, and its sort of long but ill try to explain it. Most of it you can ignore.
Anyway i'm making a tree menu with only 1 level of expansion. So you have a TreeMenu object, and this object has some Branch classes. These Branch classes have Leaf classes. That is all. On the menu there is also a little box where you can click to expand and collapse each branch. if a branch is expanded, all of its leaves are shown. if it is collapsed only the branch name is shown.
So far what I've described above works, there is a small scale compilable working program, that is alright. Theres just a few bugs to fix.
A little feature of the tree is if a branch or a leaf is selected (has been clicked on in the past) it has a blue background. This sort of works. The branch names seem to work alright, and some of the leaves. However other if you run the example i provided you can click on Leaf 1, and it will be ok, but if you click on Leaf 2 then there blue background is twice as big as it should be. But for the rest, it works ok.
This is weird to me because the same code handles any of these same situations. So it seems that i get 2 diferent results with the same code. If anyone would like to help heres some stuff you should know:
You can ignore Leaf class, i dont think theres any errors in there.
You can ignore just about all of Branch class except the update() method.
You can ignore all of TreeMenu class except the inner MouseListener class might be useful.
You can ignore TreeTester. Just the JFrame tester class.
to run the code:
javac TreeMenu.java
java TreeMenu
http://cs.ucsb.edu/~jsterling/treemenu.zip
thanks.

Answer 1

You make a good point Stefan but unfortunately I already checked that.  I have even copied the mapping (right click copy) and pasted it from the working Mapping to the bad Map (Paste) to make sure the context values were all the same.
I also opened all the queues and compared the values in each.  All values match exactly except for the result(out) queue.
In both tests I am using the same IDOC XML file. 
These are the only differences I see.
1.  The IDOC is exactly the same as far as I can tell but they come from two different source SWCV.  SAP APPL 4.7 and Steelcase_Procurement (ECC 6.0). 
2.  The working map uses a local UDF.  The bad map calls the UDF from a Function Group.  Is there a Java version difference between the two?
A better sample of the result queues look like this:
Correct Result:
Thickness of Glass: 20
Height: 10
Width: 5
Length: 18
Thickness of Glass: 10
Height: 15
Width: 8
Length: 14
Bad Result:
Thickness of Glass: 20
<null>
<null>
<null>
Width: 5
<null>
<null>
<null>
I took this chance to redesign my Variant Config output to separate the characteristics/values, but I'm still bothered that I was unable to determine what would cause the differing values.
Any ideas?
Thanks,
Matt