| Author |
Message
|
| neckert |
 Posted: Mon Apr 14, 2008 4:30 am Post subject: MB6.1: Problem with XMLNSC schema validation |
 |
|
Newbie
Joined: 14 Apr 2008
Posts: 4
|
I created a simple message flow with an MQInput node, a Compute node and an MQOutput node. I enabled validation by setting the validation property of the MQOutput node to "contentAndValue" and created a simple message set from an XML schema.
But when I run the message flow, I always receive the following error:
| Code: |
(
(0x01000000):RecoverableException = (
(0x03000000):File = 'F:\build\S000_P\src\DataFlowEngine\ImbDataFlowNode.cpp'
(0x03000000):Line = 739
(0x03000000):Function = 'ImbDataFlowNode::createExceptionList'
(0x03000000):Type = 'ComIbmMQOutputNode'
(0x03000000):Name = 'EigeneAnwendungDatenfluss#FCMComposite_1_2'
(0x03000000):Label = 'EigeneAnwendungDatenfluss.Output'
(0x03000000):Catalog = 'BIPv610'
(0x03000000):Severity = 3
(0x03000000):Number = 2230
(0x03000000):Text = 'Node throwing exception'
(0x01000000):ParserException = (
(0x03000000):File = 'F:\build\S000_P\src\MTI\MTIforBroker\GenXmlParser4\ImbXMLNSCParser.cpp'
(0x03000000):Line = 673
(0x03000000):Function = 'ImbXMLNSCParser::refreshBitStreamFromElementsCommon'
(0x03000000):Type = 'ComIbmMQInputNode'
(0x03000000):Name = 'EigeneAnwendungDatenfluss#FCMComposite_1_1'
(0x03000000):Label = 'EigeneAnwendungDatenfluss.Input'
(0x03000000):Catalog = 'BIPv610'
(0x03000000):Severity = 3
(0x03000000):Number = 5010
(0x03000000):Text = 'XML Writing Errors have occurred'
(0x01000000):ParserException = (
(0x03000000):File = 'F:\build\S000_P\src\MTI\MTIforBroker\GenXmlParser4\ImbXMLNSCParser.cpp'
(0x03000000):Line = 721
(0x03000000):Function = 'ImbXMLNSCParser::getCachedIRForMessageSet'
(0x03000000):Type = 'ComIbmMQInputNode'
(0x03000000):Name = 'EigeneAnwendungDatenfluss#FCMComposite_1_1'
(0x03000000):Label = 'EigeneAnwendungDatenfluss.Input'
(0x03000000):Catalog = 'BIPv610'
(0x03000000):Severity = 3
(0x03000000):Number = 5028
(0x03000000):Text = 'Validation is enabled but pre-processed schemas cannot be located for the specified message set '
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'MessageSet2'
)
)
)
)
)
|
I double checked the name of the message set and deployed it multiple times, but the error still occurs. No idea, what I did wrong!
Not sure whether this is important, but the broker runs on Windows XP. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Apr 14, 2008 4:35 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
How does the schema show up in the BAR file? as an XSD or a dictionary?
Are you sure that your output message matches the schema? Particuarly important is the root tag and it's namespace!
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| neckert |
| Posted: Mon Apr 14, 2008 4:53 am Post subject: |
|
|
Newbie
Joined: 14 Apr 2008
Posts: 4
|
The schema shows up as a dictionary.
The XML schema and the payload of the MQ message look as following:
| Code: |
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="comIbmDniType">
<xsd:sequence>
<xsd:element name="OU" type="xsd:string"/>
<xsd:element minOccurs="0" name="Version" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="ComIbmDni" type="comIbmDniType">
</xsd:element>
</xsd:schema>
|
| Code: |
<ComIbmDni>
<Version>1.0</Version>
<OU>OU1</OU>
</ComIbmDni>
|
Last edited by neckert on Mon Apr 14, 2008 4:59 am; edited 1 time in total |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Apr 14, 2008 4:53 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Your message set does not include XMLNSC in its list of target domains. I'll bet that the BAR file contains MessageSet2.dictionary, but not MessageSet2.xsdzip. |
|
| Back to top |
|
|
| neckert |
| Posted: Mon Apr 14, 2008 5:01 am Post subject: |
|
|
Newbie
Joined: 14 Apr 2008
Posts: 4
|
| kimbert wrote: |
| Your message set does not include XMLNSC in its list of target domains. I'll bet that the BAR file contains MessageSet2.dictionary, but not MessageSet2.xsdzip. |
You are right. The BAR file does not contain MessageSet2.xsdzip. But the Message Domain property of the used message set is set to 'XMLNSC'. |
|
| Back to top |
|
|
| neckert |
| Posted: Mon Apr 14, 2008 5:04 am Post subject: |
|
|
Newbie
Joined: 14 Apr 2008
Posts: 4
|
| By the way, I use Message Broker Toolkit V6.0.2 not V6.1; does this somehow cause the problem with the missing .xsdzip ressource? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Apr 14, 2008 5:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| neckert wrote: |
| By the way, I use Message Broker Toolkit V6.0.2 not V6.1; does this somehow cause the problem with the missing .xsdzip ressource? |
YES.
You can't add the schema as an xsdzip with the 6.0 toolkit.
Use the 6.1 toolkit for all 6.1 stuff. Use 6.0.2.x toolkit for everything else.
You really need both installed.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
