MQSeries.net :: View topic - Windows XP-Broker 7.0.1: CREATE+PARSE+VALIDATE-Part2

scravr

Windows XP - Broker 7.0.1: CREATE + PARSE + VALIDATE ----- Part 2

I could not add a replay to original case, so I opened Part2 here:

Tracing few message types validation, I found them to fail and got the right errors on trace. Debugger is not the best way to go...

Still have strange problem with a specific type; found similare request on "XML Parsing errors at MQGet node with XMLNSC parser....." topic posted here http://www.mqseries.net/phpBB2/viewtopic.php?t=54551&view=next&sid=934a2406de1c87aecdaa99a4da4ed4f1

Then on http://www-01.ibm.com/support/docview.wss?uid=swg1IC66611 it looks like a fix was added to V7.

I am runing on 7.0.0.1 and get the same error.
The XSD is opened nice and verified with XMLSpy.

I guess there is something in it that could not be validated with Broker.
Here is the trace error:

2011-03-03 15:52:06.543972 5684 UserTrace BIP5025E: XML schema validation error ''Unexpected root tag. Element "Envelope" is not a global element.'' on line '1' column '231' when parsing element ''/Root/TempParse/XMLNSC''.
Internal error codes: 5032, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according to the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set.

Same error when parsing with SOAP Domain.

Here is how message is load with MqMon:

* QLOAD Version:1.7 Created:Tue Nov 23 09:46:40 2010
* Queue = FBOC_PB_PBS_TRADE_P

A VER 2
A RPT 0
A MST 8
A EXP -1
A FDB 0
A ENC 273
A CCS 819
A FMT MQHRF2
A PRI 4
A PER 0
A MSI 414D51205553554954553033202020204CE302CD204A8905
A COI 414D51205553554954553033202020204CE302CD204A8906
A BOC 0
A RTQ XXXX_YYYY_ZZZZ
A RTM XXXXXXXX
A USR pbsuat
A ACC 0000000000000000000000000000000000000000000000000000000000000000
A AID
A PAT 28
A PAN MQSeries Client for Java
A PTD 20101118
A PTT 23100096
A AOD
A GRP 000000000000000000000000000000000000000000000000
A MSQ 1
A OFF 0
A MSF 0
A ORL -1
S "RFH "
X 000000020000019400000111000004B8
S "MQSTR "
X 00000000000004B8000000
S " <mcd><Msd>jms_text</Msd></mcd> "
X 00000060
S "<jms><Dst>queue://XXXXXXXX/XXXX_YYYY_ZZZZ</"
S "Dst><Tms>1290121800961</Tms><Dlv>2</Dlv></jms> "
X 000000E4
S "<usr><OPTR_CXT>Uuid=xxxxxxx-ccccccc-11df-8df5-ece7"
S "8c0a3d13;SerCls=-1;ReqCls=;Name=;Address=0.0.0.0"
S ";Appn=;Tran=;Domain=;Flags=32;Calling=ccccccccc"
S "cccc-sssss-sssss;</OPTR_CXT><Topic>/xx"
S "xxxxxxx/cccccc/vvvvvv</Topic></usr><Envelope xm"
S "lns=~"http://xxx.com/fff/ggggg~" xmlns:bem=~"http:"
S "//dddd.com/eeee~" messageId=~"1032200060121:001~" sc"
S "hemaVersion=~"4_08~" publishingSystemCd=~"ddd~" publ"
S "ishMessageDtm=~"2010-11-18T18:10:00~">"
X 0A
S "<Trade sequenceNumber=~"001~" isFiguredInd=~"true~" "
S "tradeDtm=~"2010-11-18T00:00:00~" bookingSystemCd=~""
S "eeeee~" tradeEntryDtm=~"2010-11-18T18:10:00~" settlem"
S "entMethodCd=~"01~" TradeTypeCd=~"CASH~">"
X 0A
S "<EventCd>NEW</EventCd>"
X 0A
...
...
...

Message set has default domain as XMLNSC withno other supported domains.
In definition there is 1 message level named Envelope as a local-complex-type with 2 local elements (Header & Body)
Both Header & Body are Type xxx:HeaderType and xxx:BodyType with Namespace http://www.zzzzzz.com/yyy
Header is Min/Max Occurs of 0/1 and Body 1/1
Header has 6 attributes.
Body a single local element min/max of 1/1 with long list of local & complex elements

There are many Types, 1 Group, and 1 ElementandAttributes name Envelope.

Here is the mxsd:

<?xml version="1.0" encoding="UTF-8"?><xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.xxxxxxx.com/bem" xmlns:bem="http://www.xxxxxxx.com/bem" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Envelope">
<xs:annotation>
<xs:documentation>BEM 3.28 (VnE)</xs:documentation>
<xs:appinfo source="WMQI_APPINFO">
<MRMessage messageDefinition="/0/Envelope;XSDElementDeclaration$MRObject"/>
</xs:appinfo>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="Header" type="bem:HeaderType"/>
<xs:element name="Body" type="bem:BodyType"/>
</xs:sequence>
</xs:complexType>
</xs:element>

...
...
...
...

Any ideas?