IBM(R)
WebSphere(R) Message Broker Toolkit Version 8.0.0.1 Interim Fix 002
This interim fix contains fixes for the following problems:
- Message flows
APAR IC86961 Renaming node causes monitoring event validation error
- BAR files
APAR IC86411 Wrong JAR file is added when referenced by the map from library
APAR IC86996, IC87019 Message flow and subflow failed to deploy in Japanese environment
APAR IC89793 The promoted configurable property default value is in CMF
- DFDL editor
APAR IC86347 DFDL fails with memory violation when parsing right-padded chars field and group with infix separator
- Graphical Data Mapper
APAR IC86379 WebSphere Message Broker V8 Toolkit, map using database gets error in some languages
- Message Modeling
APAR IC84380 Java.lang.NullPointerException when import WSDL after upgrading WebSphere Message Broker toolkit
APAR IC85579 XML Schema files with upper cased extensions were not being loaded properly
APAR IC86040 Cannot create message definition file in existing message set
APAR IC86043 XML Schema with '.' in included locations can cause build hang
APAR IC86170 Imported soapenc.xsd conflict with soapenc11.xsd
APAR IC86243 Message set fails to deploy due to the wrong import statement
APAR IC86355 The WSDL validator does not resolve the Linux location correctly
APAR IC86428 Problem with packed numeric field
APAR IC86718 Validation message was treated as an error that can cause BAR creation to fail
APAR IC86967 Some wizards and editors always appear in English
APAR IC87107 XSD files in message set projects are flagged as duplicates
APAR IC87139 Use IBM defined SOAPENV11.XSD instead of customer one
APAR IC87256 mqsicreatemsgdefsfromwsdl command adds MRM domain to message set
APAR IC87289 mqsicreatemsgdefsfromwsdl command closes message set project
APAR IC88892 Update supplied SOAPENV11.XSD to the latest level W3C standard
APAR IC87363 Fix pattern validation to be consistent with XML Schema specification.