MQSeries.net :: View topic

aks · Posted: Wed Sep 25, 2002 6:00 pm Post subject: CSD03 xml attribute problem

Hello,
I'm using validation on an MQInput node to check xml against an imported dtd with CSD03. All has been working nicely until I added #IMPLIED attributes to my dtd. After reimporting the dtd into a new message set, and sending an xml message to the queue, the validation has stopped working. The trace nows says
2002-09-26 10:39:08.602999 1988 Error BIP2628E: Exception condition detected on input node 'mfSunrise.POLISY2.Request.V001.Request XML'.
The input node 'mfSunrise.POLISY2.Request.V001.Request XML' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2002-09-26 10:39:08.602999 1988 RecoverableException BIP2230E: Error detected whilst processing a message in node 'mfSunrise.POLISY2.Request.V001.Risk Classes.FIR.SunriseXML to FIR'.
The message broker detected an error whilst processing a message in node 'mfSunrise.POLISY2.Request.V001.Risk Classes.FIR.SunriseXML to FIR'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2002-09-26 10:39:08.602999 1988 ParserException BIP5285E: Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'msSunrise.SunriseXML4'
Message Set Level : '1'
Message Format : 'XML'
Message Type Path : 'SunriseXML'
Review further error messages for an indication to the cause of the errors.
2002-09-26 10:39:08.602999 1988 ParserException BIP5354E: MTI internal error: diagnostic information 'Unexpected actualType for Element'.
An internal software error has occurred in the Message Translation Interface Parser. The diagnostic information associated with this message is: 'Unexpected actualType for Element'.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.

I know the dtd and input xml is valid but the same error, 'Unexpected actualType for Element' appears every time. My dtd has about 250 elements, but it doesn't matter if an attribute is defined to just one element or all elements, the same message appears.

If I turn validation off in the input node, then the xml messages passes through successfully. Does anyone have any suggestions? It seems that I can't use validation, when there are attributes in a dtd

Thanks
Alan