JR43921: MAP: THE NAMESPACES DECLARED ON AN ELEMENT THAT IS BEING MOVED ARE NOT COPIED TO THE TARGET ELEMENT

7.5.1.1: IBM Integration Designer V7.5.1 Fix Pack 1 for Windows
7.5.1.1: IBM Integration Designer V7.5.1 Fix Pack 1 for Linux
Version 8.0 Refresh Pack 1 for the IBM Business Process Manager products
8.0.1: IBM Integration Designer V8.0 Refresh Pack 1 for Windows
8.0.1: IBM Integration Designer V8.0 Refresh Pack 1 for Linux

APAR status

• Closed as fixed if next.

Error description

• USER AFFECTED: IID user using an XML map, with the XSLT 2.0
  generation engine in a scenario where namespaces are declared on
  elements being moved
  
  PROBLEM DETAILED DESCRIPTION: In this case, the scenario that
  causes the problem is a combination of the mediation flow having
  set a correlation context, the XML map using the root (/) of the
  SMO, and the XML map also using the XSLT 2.0 generation engine.
  In this case, when the correlation is mapped to an element of
  the same type but of different name using a Move, the namespaces
  declared on the input correlation element are not copied to the
  target element.
  

Local fix

Problem summary

• Fix planned for next V7.5.1 cumulative maintenance deliverable,
  targetting 3Q 2012.
  
  USER AFFECTED: IID user using an XML map, with the XSLT 2.0
  generation engine in a scenario where namespaces are declared on
  elements being moved
  
  PROBLEM SUMMARY: The namespaces declared on an element that is
  being moved are not copied to the target element
  
  PROBLEM DETAILED DESCRIPTION: In this case, the scenario that
  causes the problem is a combination of the mediation flow having
  set a correlation context, the XML map using the root (/) of the
  SMO, and the XML map also using the XSLT 2.0 generation engine.
  In this case, when the correlation is mapped to an element of
  the same type but of different name using a Move, the namespaces
  declared on the input correlation element are not copied to the
  target element.
  
  PROBLEM CONCLUSION: The problem is fixed by generating the XSLT
  in such a way that the namespaces will be copied to the target
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R751 PSY

     UP

• R800 PSY

     UP