| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| accessing XML fields now NULL in version 6.0 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Lillian |
 Posted: Tue Jul 24, 2007 3:10 am Post subject: accessing XML fields now NULL in version 6.0 |
 |
|
Centurion
Joined: 15 Apr 2002
Posts: 102
|
Hi . We are migrating from version 2.1 to version 6.0 and code that worked does not seem to working in version 6.0. Below is a trace of the input xml message that is parsed thru an MRM comparing the two version.
One of the parent fields is coming thru as NULL and we cannot access the children. The same message, same message set but I cannot access the LifeAsuredValuesCount field or any below LifeAsuredValues.
looking at the message set , I cannot update the properties of the elements in question as the OLifEExtension element is of "variable type"
version 6.003 trace:
(0x0300000B):ParticipationPct = 0E+0
(0x01000013):OLifEExtension = (
(0x0300000B):VendorCode = 'FSE'
(0x0300000D):LifeAsuredValues = NULL
(
(0x0300000D):@id = '1116295804_COV1_LIFE1_VALS1'
(0x0300000D): = '8'
(0x0300000D):LifeAsuredValue = NULL
(
(0x0300000D):@id = '1116295804_COV1_LIFE1_VALS1_VAL1'
(0x0300000D):Year = '1'
(0x0300000D):PremiumAmount = '69.00'
(0x0300000D):InsuredAmount = '10000'
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Version 2.1 trace :
(0x1000000)OLifEExtension = (
(0x3000000)VendorCode = 'FSE'
(0x1000000)LifeAsuredValues = (
(0x3000000)@id = '1116295804_COV1_LIFE1_VALS1'
(0x3000000)LifeAsuredValuesCount = '8'
(0x1000000)LifeAsuredValue = (
(0x3000000)@id = '1116295804_COV1_LIFE1_VALS1_VAL1'
(0x3000000)Year = '1'
(0x3000000)PremiumAmount = '69.00'
(0x3000000)InsuredAmount = '10000'
)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Jul 24, 2007 3:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you notice, the v6 element is an entirely different type than the 2.1 element.
Did you migrate the message set, or did you reimport the ACORD schema?
Is the message set Namespace aware?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Lillian |
| Posted: Tue Jul 24, 2007 3:45 am Post subject: |
|
|
Centurion
Joined: 15 Apr 2002
Posts: 102
|
| I migrated the message set and there was no update to name space settings. ( does not use namespaces) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 24, 2007 4:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The most frequently occurring problem I've run into when working with MRM-XML in v6 is having elements self-define, rather than follow the model.
If you use debug tracing, you will see messages about "element such and such" was self-defined, I think. Or you can set the Content Validation on the type describing your message to "Closed", and then enable validation in your flow. This will throw warnings about elements that are self-defined.
The most frequent reason for self-defining elements with MRM-XML is that the XML *data* has a different namespace than the message set. In your case, for example, the XML data could have a default namespace or etc, that's occuring at a higher up level than you've shown. This would then cause that higher level element (Perhaps the OLifE element itself) to be self-defining, which would make all of it's children ineligible to match the message set.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
