APAR status
Closed as fixed if next.
Error description
Message fails during schema validation when using XSD created by WBE, because WBE exports these messages without any particular order
Local fix
Problem summary
WebSphere Bisuness Events is geerating an XSD which is expecting nodes in a particular sequence order.
Problem conclusion
Temporary fix
Here's the work-around for this problem: Replace <sequence> with <choice maxOccurs="unbounded" minOccurs="0"> Remove any maxOccurs= or minOccurs= from any <element> in the <choice>.
Comments
APAR Information
APAR number
IV00405
Reported component name
WEBSPHERE BUS E
Reported component ID
5724U9000
Reported release
701
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-12
Closed date
2011-05-13
Last modified date
2011-05-13
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
R701 PSN
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTNLG","label":"WebSphere Business Events"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
13 May 2011