XML mapping editor Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Description
2.0 Limitations
3.0 Known problems and workarounds
   3.1 Array of elements are shown individually if minOccurs is not 0 or 1

1.0 Description

This release notes file contains late-breaking information about limitations and known problems and workarounds for the WebSphereR Integration Developer XML mapping editor.

2.0 Limitations

None

3.0 Known problems and workarounds

3.1 Array of elements are shown individually if minOccurs is not 0 or 1

If you define your element with minOccurs NOT equal to 0 or 1 in your XSD Schema, similar to this:

<element maxOccurs="max_integer" minOccurs="min_integer" name="elementName" type="yourType"/>

where:

two or more entries of elementName will be displayed in the XML mapping editor when you use this XSD Schema as either source or target.  If you perform a match mapping from the parent element to elementName, elementName will be mapped multiple times and can result in undesirable mapping.

Workaround 1:
Map each entry of elementName before performing match mapping from the parent element.

Workaround 2:
Set minOccurs to 0 or 1.