ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Set Issues when deploying to the Broker

Post new topic  Reply to topic
 Message Set Issues when deploying to the Broker « View previous topic :: View next topic » 
Author Message
kytem
PostPosted: Wed Jan 06, 2010 3:05 pm    Post subject: Message Set Issues when deploying to the Broker Reply with quote

Newbie

Joined: 06 Dec 2009
Posts: 7

Hi,

I'm experiencing the following error when deploying my message flow.

BIP5029E: Error 'a-props-correct.2: Invalid value constraint value '1' in attribute 'mxencrypted'.' was encountered at line '138' while preprocessing XML Schema file 'com/ibm/www/maximo/MXMeta.xsd' in message set 'MMISMessageSet'

The XMLNSC parser is preprocessing the XML Schemas for the message set and it has encountered an error.

Check that the XML Schemas in the message set are valid.


The field in question mxencrypted is boolean, and in the MXMeta.xsd, the boolean data type has a value constraint of 0 or 1.

When I remove the 0 or 1 constraint the flow deploys fine.

Has anybody else experienced this issue, as I believe 0 or 1 is a valid value for a boolean field?
Back to top
View user's profile Send private message
smdavies99
PostPosted: Wed Jan 06, 2010 11:31 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Isn't 0 or 1 implicit for a boolean 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
View user's profile Send private message
kimbert
PostPosted: Thu Jan 07, 2010 2:18 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

I had to look up the XML schema specification to answer this one.

From the primer: http://www.w3.org/TR/xmlschema-0/#CreatDt
Quote:
XML Schema defines twelve facets which are listed in Appendix B. Among these, the enumeration facet is particularly useful and it can be used to constrain the values of almost every simple type, except the boolean type.


And confirmed by the real spec: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#boolean
Quote:
3.2.2.3 Constraining facets

boolean has the following ·constraining facets·:

* pattern
* whiteSpace


So your schema is incorrect. I will admit, though, that the error message is quite misleading. It should have told you that xs:boolean cannot have enumeration facets, instead of complaining about the value of the enumeration facet.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Set Issues when deploying to the Broker
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.