Author |
Message
|
akidase |
Posted: Wed Dec 05, 2012 8:26 am Post subject: Validate Node Problem. |
|
|
Centurion
Joined: 10 Jan 2011 Posts: 124
|
Validate Node isn't throwing an exception nor passing the message.
I don't understand the problem. Please help.
There are two functionality(based on interaction with end systems) of my message flow and for each, the structure created is same. However one passes through Validation properly and the other doesn't. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Dec 05, 2012 8:32 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
Attach two separate Trace nodes, one to the Failure terminal and one to the Match terminal. Set the pattern for the Trace node to
Code: |
Root:
${Root}
===
LocalEnvironment:
${LocalEnvironment}
===
ExceptionList:
${ExceptionList}
===
Environment
${Environment}
===
${CURRENT_TIMESTAMP}
======================= |
and the output to File with a path like C:/TEMP/Trace1.txt for the first trace node and C:/TEMP/Trace2.txt for the second. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
kimbert |
Posted: Wed Dec 05, 2012 9:00 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Please list all of the places where you have looked for the exception. |
|
Back to top |
|
 |
akidase |
Posted: Wed Dec 05, 2012 9:12 am Post subject: |
|
|
Centurion
Joined: 10 Jan 2011 Posts: 124
|
I have enabled trace and saw that it was failing with Schema validation error.
I have rectified that message part and found it working.
However the node doesn't throw an error, somehow. I am confused as to why the node didn't throw the error.
Code: |
UserTrace BIP5026E: XML schema validation error: 'cvc-complex-type.2.4.a: Expecting element with local name "ApplicantID" but saw "ApplicantFirstName".' Element: '/Root/XMLNSC' Internal error codes: 5004, 2. Line: 1, Column: 507
This error was reported by the XMLNSC parser. The message tree is not valid according to the message definitions in the message set.
The message tree is not valid according to the message definition files in the message set.
- Check that the elements and attributes in the message tree are declared in the message set.
- Check that all attributes in the message tree have been cast as (XMLNSC.Attribute) in the message tree.
- Check that any values of types gDate, gYear, gMonth, gDay, gYearMonth, gMonthDay have been cast as (XMLNSC.gDate), (XMLNSC.gYear) and so on, in the message tree.
- Check that any values of type base64Binary have been cast as (XMLNSC.base64Binary) in the message tree.
The message tree is converted to an XML bitstream before being validated. The line and column number are the coordinates of the error in the XML bitstream. |
|
|
Back to top |
|
 |
nathanw |
Posted: Wed Dec 05, 2012 9:15 am Post subject: |
|
|
 Knight
Joined: 14 Jul 2004 Posts: 550
|
version? _________________ Who is General Failure and why is he reading my hard drive?
Artificial Intelligence stands no chance against Natural Stupidity.
Only the User Trace Speaks The Truth  |
|
Back to top |
|
 |
akidase |
Posted: Wed Dec 05, 2012 9:19 am Post subject: |
|
|
Centurion
Joined: 10 Jan 2011 Posts: 124
|
BIPmsgs en_US
Console CCSID=819, ICU CCSID=819
Default codepage=ISO-8859-1, in ascii=ISO-8859-1
JAVA console codepage name=ISO-8859-1
BIP8996I: Version: 7004
BIP8997I: Product: WebSphere Message Broker
BIP8998I: CMVC Level: S700-FP04
BIP8999I: Build Type: Production, 64 bit, rios_aix_4 |
|
Back to top |
|
 |
kimbert |
Posted: Wed Dec 05, 2012 9:21 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
A validation error is not always a WMB exception. It depends on the Failure Action setting on the node. Please quote the values of the 'Validation' and 'Failure Action' properties. |
|
Back to top |
|
 |
akidase |
Posted: Wed Dec 05, 2012 9:22 am Post subject: |
|
|
Centurion
Joined: 10 Jan 2011 Posts: 124
|
Validation -
Validate - Content and Value
FailureAction - Exception. |
|
Back to top |
|
 |
|