Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » OCL » How to disable a built-in constraint
How to disable a built-in constraint [message #11860] Sat, 17 March 2007 13:04 Go to next message
Eclipse User
Originally posted by: maiera.de.ibm.com

Hi,
in the work on the UML Profile for CIM, we are encountering a built-in
constraint of Error severity which we would like to get rid of, or disable:

Redefining element '<<cIM_Property, property_Constraints>> <Property>
PropUint8 : PropUint8_Enum' is not consistent with redefined element
'<<property_Constraints, cIM_Property>> <Property> PropUint8 : uint8'.

The situation is that in CIM, it is possible to add the ValueMap
qualifier to a redefined property that previously did not have one.
Since we are now using UML Enumerations to map properties qualified with
the CIM ValueMap qualifier, adding this qualifier in a subclass changes
an integer type in the superclass to an enumeration type in the subclass.

This understandably causes the built-in constraint to fire.

My question is:
- Is it possible to disable this particular built-in constraint ?

Andy
Re: How to disable a built-in constraint [message #13474 is a reply to message #11860] Sun, 18 March 2007 09:24 Go to previous messageGo to next message
Eclipse User
Originally posted by: cdamus.ca.ibm.com

Hi, Andy,

This is one of the constraints defined by the UML specification. Is that
what you mean by "built-in"? IIRC, you are using RSA, in which case this
constraint can be disabled in the "Modeling / Model Validation" preference
page (I think that's the path). You should also be able to disable it
using the Quick-fix in the Problems view. I don't think there's a means
to disable it for elements with your stereotype only.

Cheers,

Christian


Andreas Maier wrote:

> Hi,
> in the work on the UML Profile for CIM, we are encountering a built-in
> constraint of Error severity which we would like to get rid of, or disable:

> Redefining element '<<cIM_Property, property_Constraints>> <Property>
> PropUint8 : PropUint8_Enum' is not consistent with redefined element
> '<<property_Constraints, cIM_Property>> <Property> PropUint8 : uint8'.

> The situation is that in CIM, it is possible to add the ValueMap
> qualifier to a redefined property that previously did not have one.
> Since we are now using UML Enumerations to map properties qualified with
> the CIM ValueMap qualifier, adding this qualifier in a subclass changes
> an integer type in the superclass to an enumeration type in the subclass.

> This understandably causes the built-in constraint to fire.

> My question is:
> - Is it possible to disable this particular built-in constraint ?

> Andy
Re: How to disable a built-in constraint [message #13537 is a reply to message #13474] Sun, 18 March 2007 14:05 Go to previous message
Eclipse User
Originally posted by: maiera.de.ibm.com

Hi Christian,
it works, thanks!

Andy

Christian W. Damus wrote:
> Hi, Andy,
>
> This is one of the constraints defined by the UML specification. Is
> that what you mean by "built-in"? IIRC, you are using RSA, in which
> case this constraint can be disabled in the "Modeling / Model
> Validation" preference page (I think that's the path). You should also
> be able to disable it using the Quick-fix in the Problems view. I don't
> think there's a means to disable it for elements with your stereotype only.
>
> Cheers,
>
> Christian
>
>
> Andreas Maier wrote:
>
>> Hi,
>> in the work on the UML Profile for CIM, we are encountering a built-in
>> constraint of Error severity which we would like to get rid of, or
>> disable:
>
>> Redefining element '<<cIM_Property, property_Constraints>> <Property>
>> PropUint8 : PropUint8_Enum' is not consistent with redefined element
>> '<<property_Constraints, cIM_Property>> <Property> PropUint8 : uint8'.
>
>> The situation is that in CIM, it is possible to add the ValueMap
>> qualifier to a redefined property that previously did not have one.
>> Since we are now using UML Enumerations to map properties qualified
>> with the CIM ValueMap qualifier, adding this qualifier in a subclass
>> changes an integer type in the superclass to an enumeration type in
>> the subclass.
>
>> This understandably causes the built-in constraint to fire.
>
>> My question is:
>> - Is it possible to disable this particular built-in constraint ?
>
>> Andy
>
Previous Topic:How to access name of EnumerationLiteral
Next Topic:Null exception in constraints on EnumerationLiteral
Goto Forum:
  


Current Time: Wed Jul 23 18:16:24 EDT 2014

Powered by FUDForum. Page generated in 0.01562 seconds