| Author |
Message
|
| satya22777 |
 Posted: Thu Feb 21, 2008 7:38 am Post subject: XML Validator Node Issue |
 |
|
Apprentice
Joined: 03 Apr 2006
Posts: 31
|
Hello All,
I'm using WMB v6.1 on Windows 2003 server platform along with WMQ v6. My flow looks like
FileInputNode-->ComputeNode-->XmlValidatorNode--->MQOutputNodes
One MQOutputNode is connected to the Invalid termianl of XmlValidatorNode and another MQOutputNode is connected to the Out terminal.
I installed XmlValidatorNode using IA9A package.
In the compute node I'm mapping '.CSV' file into XMLNS Format.
I've configured XmlValidatorNode like,
file://"namespace1" file:///path of the .xsd file.
in xsi:schemaLocation property.
I'm getting error like
| Quote: |
| Error:CHARACTER:Error: [1:289] cvc-elt.1: Cannot find the declaration of element 'pidx:Invoice'. |
I tried to validate the output xml file in XMLSpy it is validating perfectly.
but always the message is going to the invalid terminal. i tried several times.
can anybody help me in working with this node.
Thanks in advance. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Feb 21, 2008 7:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You don't need the XMLValidator node in Broker v6.1.
The XMLNSC Parser will validate against the schema for you.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Feb 21, 2008 10:36 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Jeff said:
| Quote: |
| The XMLNSC Parser will validate against the schema for you. |
...and it will use a lot less CPU. |
|
| Back to top |
|
|
| satya22777 |
| Posted: Thu Feb 21, 2008 10:36 am Post subject: |
|
|
Apprentice
Joined: 03 Apr 2006
Posts: 31
|
Hi Jeff,
Thanks for your response. I have the below questions to clarify regading validation against XSD,
How Can the schema be provided externally (i.e without creating message sets so that I can dynamically use the solution)?.
What level of validation does XMLNS solution provide? Does it error out on first encounter of mismatch or does it provide a list of errors?
Thanks in adavnce. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Feb 21, 2008 11:08 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| How Can the schema be provided externally (i.e without creating message sets so that I can dynamically use the solution)?. |
You can create one message set per schema, and change the Message Set property to select which one you validate against.
| Quote: |
| What level of validation does XMLNS solution provide? |
Fully W3C compliant.
| Quote: |
| Does it error out on first encounter of mismatch or does it provide a list of errors? |
By default it stops after the first error. However, if you set Failure Action to 'ExceptionList' it will tolerate some errors ( mainly those which involve attribute values not matching their facets ).
Recovering from errors involving element content ( like an element missing from a sequence ) is tricky because
a) there are often a range of possible errors which could be reported and
b) a single error early in the message can cause a huge cascade of secondary errors.
Hence the restriction. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Feb 21, 2008 11:16 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| crossland |
| Posted: Mon Oct 13, 2008 2:49 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
Does the validation provided with 6.1 provide the same level of validation of xml against a schema, as that provided by the xml validation node supplied with the 1a9a supportpac?
Thanks,
Tim |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Oct 13, 2008 4:38 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi,
It depends on what you mean by 'same level of validation'?
XMLNSC is 100% compliant with the W3C XML Schema specification. IA9A is based on the Xerces parser, which also complies fully with the W3C schema spec. So XMLNSC will be at least as 'strict' as IA9A. Does that answer your question? |
|
| Back to top |
|
|
|
|
