| Author |
Message
|
| Y75 |
 Posted: Mon Sep 16, 2013 7:14 am Post subject: Build Tree using XML schema data types |
 |
|
Apprentice
Joined: 29 Jul 2013
Posts: 32
|
I have my xml schema in a library; library is referred in the application I constructed my message flow. While using XMLNSC parser in MQ input node, I can't convert my xml message to appropriate data types. All of them are considered as character in message tree.
Infact, the option to "Build Tree using XML schema data types" is disabled. Should it be enabled all the time if I am using library? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Sep 16, 2013 7:21 am Post subject: Re: Build Tree using XML schema data types |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Y75 wrote: |
| I have my xml schema in a library; library is referred in the application I constructed my message flow. |
Can we infer from your use of this terminology that you're using WMBv8.0.0.n? If so, what's the value of n?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Sep 16, 2013 7:21 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Y75 |
| Posted: Mon Sep 16, 2013 7:35 am Post subject: |
|
|
Apprentice
Joined: 29 Jul 2013
Posts: 32
|
I am using IIB tookit v9.0.0.
I think difference between my code and validation sample is that validation sample uses message set while I just have my schema in library.
I have tried to set parse timing to complete; the option is still not enabled. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Sep 16, 2013 8:24 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Here is the law of 'Build tree using XML Schema'.
- The XMLNSC parser cannot build the tree using schema types if it is not looking at the schema. So it is essential to set Validation to 'Content and Value' if you want to enable this option.
- In the the XMLNSC domain this property defaults to 'No' because the first ( v6.0) release of the XMLNSC domain did not support schema validation, and it therefore could only build CHARACTER message trees.
- In the SOAP domain, which arrived with v6.1, it defaults to 'Yes' because there was no need for backward compatibility.
In summary: this is nothing to do with libraries or applications. You do need to set that property if you want non-CHARACTER types in the message tree. And you must switch on validation.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| Y75 |
| Posted: Mon Sep 16, 2013 11:54 am Post subject: |
|
|
Apprentice
Joined: 29 Jul 2013
Posts: 32
|
| Thanks Kimbert ! Switching on validation on content and value did the trick. |
|
| Back to top |
|
|
|
|
