| Author |
Message
|
| edasnarik |
 Posted: Thu Mar 19, 2009 10:05 pm Post subject: Problem with Message set |
 |
|
Acolyte
Joined: 10 Mar 2009
Posts: 61
|
| Code: |
Severity and Description Path Resource Location Creation Time Id
MRM domain: Simple Type Definition '#Boolean_NoID' has a base type that is 'boolean' and contains pattern facets, which is not supported and will be ignored by the broker. Project_MSP/Project_MS Proj_acord-pcs-v1_11_0-nodoc-codes.mxsd line 1 1237470640281 6
|
| Code: |
Severity and Description Path Resource Location Creation Time Id
The group definition '#EDIT2_CHOICE' is circularly defined, which is prohibited. Project_MSP/CTI_AUTOCOVERAGE_EPAS_MS Proj_acord-pcs-v1_11_0-nodoc-codes.mxsd line 0 1237470640281 5 |
Any Idea ? |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Thu Mar 19, 2009 10:40 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
no 
_________________
Regards, Butcher |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Mar 19, 2009 11:33 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
We need to see bits of the actual messge set XML before any real help can be given.
The second one is fairly self explanatory. Something is referencing itself.
How was the message set created? Was it an import from an XSD or Copybook?
Or was it created manually? If it was the latter then these mistakes do sometimes happen.
It is also a good idea to generate an XSD from the message set and then use something like XMLSpy to validate/correct it before importing it back into broker.
_________________
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 |
|
|
| Vitor |
| Posted: Fri Mar 20, 2009 12:43 am Post subject: Re: Problem with Message set |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| edasnarik wrote: |
| Any Idea ? |
Errors about the message set. Almost certainly. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Mar 20, 2009 2:03 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
These are warnings in the Problems view of the message definition file editor. The MRM parser does not support some of the features of the W3C XML Schema specification, and it is trying to be honest about it.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/topic/com.ibm.etools.mft.doc/ad09920_.htm
If you are successfully using your message set anyway then there's no need to be concerned - these are warnings, not errors. If you are processing XML ( you didn't say ) and you need 100% accurate schema validation, move to v6.1 and use XMLNSC instead of MRM. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Fri Mar 20, 2009 2:12 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
i've managed to replicate the first warning (its not an error) by creating (in XMLSpy) a boolean simple type as follows:
| Code: |
<xs:simpleType name="sampleboolean">
<xs:restriction base="xs:boolean">
<xs:whiteSpace value="collapse"/>
<xs:pattern value="xxxx"/>
</xs:restriction>
</xs:simpleType> |
It looks like broker doesnt support the pattern restrictions on the boolean type, please check you dont have any.... |
|
| Back to top |
|
|
|
|
