Author |
Message
|
mbsa |
Posted: Sun Jun 30, 2013 3:58 pm Post subject: SOAPINPUT Node validation failure |
|
|
Apprentice
Joined: 04 Mar 2013 Posts: 41
|
Hi,
I am using WMB 8.0.My saopinput node validations are happening if the message is like below from soapui.
Code: |
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:gkp="http://DV01">
<soapenv:Header/>
<soapenv:Body>
<gkp:DV01_01Operation>
<DV01_01In>
-----
</DV01_01In>
</gkp:DV01_01Operation>
</soapenv:Body>
</soapenv:Envelope>
|
I have parsing as on demand and validation as content &value.
But the message from Datapower is coming to message broker as below
Code: |
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:gkp="http://DV01">
<soapenv:Header/>
<soapenv:Body>
<gkp:DV01_01Operation>
<DV01_01In>
-----
</DV01_01In>
</gkp:DV01_01Operation>
</soapenv:Body>
</soapenv:Envelope>
|
I see the soap validations are not happening for the second message and i see that only difference between them is
<?xml version="1.0" encoding="UTF-8"?> added.
why it is happening and how can it be resolved?Any help is appreciated. |
|
Back to top |
|
 |
smdavies99 |
Posted: Sun Jun 30, 2013 9:51 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
The XML Header tells the parser what Character set the rest of the message is in.
I'd suspect that there is some character that is represented in a way that needs UTF-8.
As this is a SOAP message, load it into SOAP/UI and validate it there. It will tell you where the issue with the message is. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
kimbert |
Posted: Sun Jun 30, 2013 11:51 pm Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
I see the soap validations are not happening for the second message |
What does that mean, exactly? Are you getting validation errors? If so, please quote them. |
|
Back to top |
|
 |
mbsa |
Posted: Mon Jul 01, 2013 4:07 am Post subject: |
|
|
Apprentice
Joined: 04 Mar 2013 Posts: 41
|
Code: |
I see the soap validations are not happening for the second message
|
I have put some validations like enumeration and length on some fields.
In the first message i am seeing xsd validation errors like
Code: |
A schema validation error has occurred while parsing the XML document. The value "6" is not valid with respect to the enumeration facet for type "#Anonymous". It must be a value from the enumeration.
|
But this is not happening in the second message where we added
<?xml version="1.0" encoding="UTF-8"?> to the message. |
|
Back to top |
|
 |
kimbert |
Posted: Mon Jul 01, 2013 4:22 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
The XML declaration is not the problem.
Perhaps your message flow is not triggering any parsing of the input message? Try setting Parse Timing to 'Immediate'. |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Jul 01, 2013 4:22 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
How about showing us the schema definition for this errant field? _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mbsa |
Posted: Mon Jul 01, 2013 7:00 am Post subject: |
|
|
Apprentice
Joined: 04 Mar 2013 Posts: 41
|
Hi Kimbert,
It works if i change the Parse timing to Immediate.Thanks. |
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Jul 01, 2013 9:30 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
mbsa wrote: |
Hi Kimbert,
It works if i change the Parse timing to Immediate.Thanks. |
So what about the Validation? Are you still doing that with the new parser timing?
IMHO, you have just avoided the issue, not solved it once and for all.
This sort of problem seem to come back and bite you when you least expected it. Sort of like a King Cobra. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
mbsa |
Posted: Mon Jul 01, 2013 10:51 am Post subject: |
|
|
Apprentice
Joined: 04 Mar 2013 Posts: 41
|
Hi smdavies99,
Validations are still in place.I have the validation option as Content&value.
But they were getting triggered only When i changed the parser option from On demand to immediate. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Jul 01, 2013 10:56 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
|
Back to top |
|
 |
smdavies99 |
Posted: Mon Jul 01, 2013 11:12 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Ok, so you are not seeing the problem due to changing the parser settings.
Do you really think that you have solved the original problem?
IMHO, you have just hidden it for a while.
What are you doing to actually find the root cause of the problem.
Remember the Scorpion. It has a nice little sting in the tail, just like your problem, it won't go away. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
|