| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem Validating XML Message against dtd |
« View previous topic :: View next topic » |
| Author |
Message
|
| TonyD |
 Posted: Sun Feb 02, 2003 9:55 pm Post subject: Problem Validating XML Message against dtd |
 |
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
I have imported a large dtd amd am trying to carry out validation against elements and attributes. I get the following message for a number of elements or attributes (but not all) even though they are clearly in the input message:
| Quote: |
2003-02-03 17:04:15.670999 768 UserTrace BIP5374E: Message Validation failure. An element, that has been deemed complete, does not meet the minOccurs constraint.
Element, name, has 0 instances on the logical tree, but has been defined or qualified with a minOccurs Constraint of 1 within it's parent type/element t_person_cmType of index 1.
Adjust the minOccurs Constraint downwards and redeploy to the broker or increase the instances of the element in the bitstream or through ESQL. |
In case it was problems with the quite large and complex dtd I tried with a redbook example, the 'people/person' message and got the same result (the trace output above).
The message shows in the trace output and the 'element, name' is definitely there.
| Quote: |
(0x100001B)MRM = (
(0x1000013)person = (
(0x300000B)location = 'London'
(0x300000B)age = '23'
(0x1000013)name = (
(0x300000B)first = 'Jack'
(0x300000B)last = 'Bloggs'
)
(0x300000B)email = 'fredb@clear.net.nz'
)
)
|
The flow successfully did an enumeration validation against 'first' however.
I am wondering if any one has come across this behaviour or can suggest a solution. I thought, in the case of the large dtd, that I had narrowed the problem down to 'empty' elements with attributes, but that is not the case with the above example; 'element, person' has sub-elements 'name' and 'email'.
In view of the WMQI 2.1 CSD history so far I thought I should check with others before spending too much more time trying to figure out how to get around the problem. |
|
| Back to top |
|
 |
| kwelch |
| Posted: Wed Aug 20, 2003 9:53 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Tony,
Did you ever find a resolution to this? We are experiencing the same problem trying to validate. When I try with my more complex message against the DTD I imported, I get the error you sited above where the element is definitely there but for some reason it is not recognized. I tried with a very small dtd with every field present and it validated but then when I removed one of the supposed required fields it still validated.
Has anyone got validation to work successfully? How did you do it?
Thanks,
Karen |
|
| Back to top |
|
|
| Craig B |
| Posted: Wed Aug 20, 2003 10:24 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Hi,
There is a known problem that was discovered on WMQI V2.1 CSD05 which erroneously issues the BIP5374E error message even when the minOccurs constraints has been satisfied. This error will be generated on exit of the Compute node when Compute node validation is used. If you think you are experiencing this error and you are sure that this BIP5374E should not be generated, then contact your IBM support centre regarding this problem. To help them out you could quote the number D27730, that may have some meaning to them.
_________________
Regards
Craig |
|
| 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
|
|
|
|
