| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Input Node validation failure of Element Attributes |
« View previous topic :: View next topic » |
| Author |
Message
|
| Tungsten |
 Posted: Mon Dec 12, 2005 7:00 pm Post subject: Input Node validation failure of Element Attributes |
 |
|
Newbie
Joined: 07 Dec 2005
Posts: 4
|
Hi, and thanks in advance,
I am currently encountering a validation failure between the sample XML message I am using in my flow against it's schema.
A snippet of the XML Message (and the XML structure behind the element that is causing the errors) is:
| Quote: |
<?xml version="1.0" encoding="UTF-8" ?>
<?Siebel-Property-Set EscapeNames="false"?>
<SampleMessage xmlns="http://www.siebel.com/xml/PublishAttachmentsInterface"
MessageId="1-GW9RO" MessageType="Integration Object" IntObjectName="Action Attachments Interface" IntObjectFormat="Sample Hierarchical">
<ListOfAttachments>
<Attachment>
<FileAttachment
EndOfData="true" Extension="xls" AttachmentIsTextData="false" ContentId="1-GW9RP" TimedOut="false">
SampleDataSampleDataSampleDataSampleDataSampleDataSampleDataSampleDataSampleData</FileAttachment>
</Attachment>
</ListOfAttachments>
</SampleMessage>
|
And a snippet of the XML schema I am using looks like follows:
| Quote: |
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.siebel.com/xml/PublishAttachmentsInterface"
xmlns:xsdLocal="http://www.siebel.com/xml/PublishAttachmentsInterface"
attributeFormDefault="unqualified"
elementFormDefault="qualified">
<xsd:element name="SampleMessage" type="xsdLocal:SampleMessage" />
<xsd:complexType name="SampleMessage">
<xsd:sequence>
<xsd:element name="ListOfAttachments" type="xsdLocal:ListOfAttachments" minOccurs="0" maxOccurs="1" />
</xsd:sequence>
<xsd:attribute name="MessageId" type="xsd:string" />
<xsd:attribute name="MessageType" type="xsd:string" />
<xsd:attribute name="IntObjectName" type="xsd:string" />
<xsd:attribute name="IntObjectFormat" type="xsd:string" />
</xsd:complexType>
<xsd:complexType name="ListOfAttachments">
<xsd:sequence>
<xsd:element name="Attachment" type="xsdLocal:Attachment" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Attachment">
<xsd:sequence>
<xsd:element name="FileAttachment" type="xsdLocal:SiebelXmlAttachmentType" minOccurs="0" maxOccurs="1" />
</xsd:sequence>
<xsd:attribute name="operation" type="xsd:string" />
<xsd:attribute name="searchspec" type="xsd:string" />
</xsd:complexType>
<xsd:complexType name="SiebelXmlAttachmentType">
<xsd:simpleContent>
<xsd:extension base="xsd:base64Binary">
<xsd:attribute name="EndOfData" use="optional" type="xsd:string"></xsd:attribute>
<xsd:attribute name="Extension" use="optional" type="xsd:string"></xsd:attribute>
<xsd:attribute name="AttachmentIsTextData" default="false" use="optional" type="xsd:string"></xsd:attribute>
<xsd:attribute name="ContentId" use="optional" type="xsd:string"></xsd:attribute>
<xsd:attribute name="TimedOut" default="false" use="optional" type="xsd:string"></xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:schema>
|
To my amateur eyes everything seems fairly peachy with the schema and message, and they both validate against each other in an XML validator, however, I get the following error when processing my sample message:
| Quote: |
Event Type: Error
Event Source: BIPv500
Event Category: None
Event ID: 5339
Date: 13/12/2005
Time: 1:22:08 PM
User: N/A
Computer: [Computer Name]
Description:
([Broker].[Execution Group]) Mismatch between message tree and logical definition
While writing the message, the message tree did not match the logical structure of the message. The problem was encountered while attempting to write element 'EndOfData' in message set 'MB93R24002001'.
This problem is usually caused by a badly-structured input message. It can also be caused by a badly-structured output message tree. Check that the structure of the input message matches the logical structure of the message. Check that elements defined as simple elements do not have child elements. If necessary, check that elements occur in the correct sequence, and with the correct number of repeats. If you have modified the message set or message type property in your message flow, check that these are correct.
|
The thing that's bugging me with this is that the attributes in the root element don't encounter any errors, however, the attributes in the FileAttachment element are... I am fairly new to using MQ, so your advice/assistance is much appreciated!
Cheers!  |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Dec 13, 2005 4:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Can you post a trace output of the message tree before it goes to the MQOutput node?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
