JR45120: NAMESPACE DECLARATIONS IN TWO SEPARATE MONITOR MODELS NOT PROPERLY MERGED

IBM Business Monitor development toolkit V8.0.1 Fix Pack 1 (8.0.1.1)

APAR status

• Closed as fixed if next.

Error description

• When combining two monitor models in Integration Designer, if
  both monitor models use the same namespace prefix but with
  different namespace URIs, the namespace declarations are not
  properly merged, resulting in validation errors in the combined
  monitor model.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the monitor model editor feature   *
  *                  in IBM Integration Designer.                *
  ****************************************************************
  * PROBLEM DESCRIPTION: When combining two monitor models in    *
  *                      Integration Designer, if both monitor   *
  *                      models use the same namespace prefix    *
  *                      but with different namespace URIs, the  *
  *                      namespace declarations are not          *
  *                      properly merged, resulting in           *
  *                      validation errors in the combined       *
  *                      monitor model.                          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The two monitor models may use the same namespace prefix to
  declare different namespace URIs.  As a result, the namespace
  prefix used in the combined monitor model may reference the
  wrong namespace.
  When combining the monitor models, the code should keep track
  of the namespace prefixes used by the two monitor models, and
  create a new (unique) prefix to be used in the combined
  monitor model.
  This issue will be fixed in a future maintenance release of
  IBM Integration Designer Version 8.0.1.
  

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

• R750 PSY

     UP