Home » Modeling » Epsilon » [Epsilon] Default values in HUTN
| | | |
Re: [Epsilon] Default values in HUTN [message #843 is a reply to message #814] |
Mon, 13 October 2008 15:24 |
Louis Rose Messages: 440 Registered: July 2009 Location: York, United Kingdom |
Senior Member |
|
|
Hi Héctor,
In UML 2.1,, the endType and relatedElement features of Assocation have
a lowerbound of 1, signifying that a value is required, when
instantiating a valid UML model.
We are now enforcing this constraint with HUTN, so you'll need to update
your HUTN source files accordingly.
We don't have any plans to change this, but let us know if you find it
too restrictive - we'll consider your feedback carefully.
Cheers,
Louis.
Héctor Iturria wrote:
> Hi,
>
> As you have said, it has solved my problems except for the references.
> Do I really need to change the hutn files and add the information or is
> something that is going to be fixed too?
>
> For example, in associations I still have to specify the endType and
> relatedElement, before I had not.
>
> Many thanks,
> Héctor Iturria
>
|
|
| |
Re: [Epsilon] Default values in HUTN [message #928 is a reply to message #900] |
Wed, 15 October 2008 17:55 |
Dimitrios Kolovos Messages: 1776 Registered: July 2009 |
Senior Member |
|
|
Hi Hector,
This happens because relatedElement and endType are both derived (and
thus unsettable references). I've updated the validation module to
handle such cases and committed the changes to the SVN. Now saving your
HUTN file should bring up 3 errors:
1) Association1 must specify a value for the following reference
features: memberEnd (as memberEnd has a lower-bound of 2)
2) Feature endType is not changeable
3) Feature relatedElement is not changeable
Thanks a lot for reporting this!
Cheers,
Dimitrios
Héctor Iturria wrote:
> Hi,
>
> It is not too much restrictive, but I was adding the definition of the
> properties in the HUTN files and I got some errors. I get no errors when
> coding, just when I save the file to generate the model.
>
> The error:
>
> org.eclipse.epsilon.hutn.exceptions.HutnGenerationException: Internal
> error: java.lang.UnsupportedOperationException
>
> raises from the property endType or relatedElement of an Association
> element.
>
> I send you a HUTN file and the console output.
>
> Many thanks,
> Héctor Iturria
>
>
>
>
> Louis Rose escribió:
>> Hi Héctor,
>>
>> In UML 2.1,, the endType and relatedElement features of Assocation
>> have a lowerbound of 1, signifying that a value is required, when
>> instantiating a valid UML model.
>>
>> We are now enforcing this constraint with HUTN, so you'll need to
>> update your HUTN source files accordingly.
>>
>> We don't have any plans to change this, but let us know if you find it
>> too restrictive - we'll consider your feedback carefully.
>>
>> Cheers,
>> Louis.
>>
>> Héctor Iturria wrote:
>>> Hi,
>>>
>>> As you have said, it has solved my problems except for the
>>> references. Do I really need to change the hutn files and add the
>>> information or is something that is going to be fixed too?
>>>
>>> For example, in associations I still have to specify the endType and
>>> relatedElement, before I had not.
>>>
>>> Many thanks,
>>> Héctor Iturria
>>>
>
|
|
| |
Re: [Epsilon] Default values in HUTN [message #988 is a reply to message #958] |
Thu, 16 October 2008 08:24 |
Dimitrios Kolovos Messages: 1776 Registered: July 2009 |
Senior Member |
|
|
Hi Hector,
Thanks (again) for reporting this! Should be fixed now :)
Cheers,
Dimitrios
Héctor Iturria wrote:
> Hi!
>
> I got the 3 errors and I have already updated all my models. I am almost
> there...but not yet :)
>
> Now what it raises an error are enumerations. For example, in one of my
> HUTN files (based on the UML 2.1 metamodel) I have this fragment of code:
>
> Property "dst"{
> name: "dst"
> type: Class "Class2"
> aggregation: composite
> upper: 1
> }
>
> I have followed the example of your blog to specify the property
> aggregation, but I don't know if it is really a bug or I missed something.
>
> Again, I attach the output with the info of the error.
>
>
> Many thanks!
> Héctor Iturria
>
>
> Dimitrios Kolovos escribió:
>> Hi Hector,
>>
>> This happens because relatedElement and endType are both derived (and
>> thus unsettable references). I've updated the validation module to
>> handle such cases and committed the changes to the SVN. Now saving
>> your HUTN file should bring up 3 errors:
>>
>> 1) Association1 must specify a value for the following reference
>> features: memberEnd (as memberEnd has a lower-bound of 2)
>>
>> 2) Feature endType is not changeable
>> 3) Feature relatedElement is not changeable
>>
>> Thanks a lot for reporting this!
>>
>> Cheers,
>> Dimitrios
>>
>> Héctor Iturria wrote:
>>> Hi,
>>>
>>> It is not too much restrictive, but I was adding the definition of
>>> the properties in the HUTN files and I got some errors. I get no
>>> errors when coding, just when I save the file to generate the model.
>>>
>>> The error:
>>>
>>> org.eclipse.epsilon.hutn.exceptions.HutnGenerationException: Internal
>>> error: java.lang.UnsupportedOperationException
>>>
>>> raises from the property endType or relatedElement of an Association
>>> element.
>>>
>>> I send you a HUTN file and the console output.
>>>
>>> Many thanks,
>>> Héctor Iturria
>>>
>>>
>>>
>>>
>>> Louis Rose escribió:
>>>> Hi Héctor,
>>>>
>>>> In UML 2.1,, the endType and relatedElement features of Assocation
>>>> have a lowerbound of 1, signifying that a value is required, when
>>>> instantiating a valid UML model.
>>>>
>>>> We are now enforcing this constraint with HUTN, so you'll need to
>>>> update your HUTN source files accordingly.
>>>>
>>>> We don't have any plans to change this, but let us know if you find
>>>> it too restrictive - we'll consider your feedback carefully.
>>>>
>>>> Cheers,
>>>> Louis.
>>>>
>>>> Héctor Iturria wrote:
>>>>> Hi,
>>>>>
>>>>> As you have said, it has solved my problems except for the
>>>>> references. Do I really need to change the hutn files and add the
>>>>> information or is something that is going to be fixed too?
>>>>>
>>>>> For example, in associations I still have to specify the endType
>>>>> and relatedElement, before I had not.
>>>>>
>>>>> Many thanks,
>>>>> Héctor Iturria
>>>>>
>>>
>
|
|
| | | |
Re: [Epsilon] Default values in HUTN [message #561001 is a reply to message #814] |
Mon, 13 October 2008 15:24 |
Louis Rose Messages: 440 Registered: July 2009 Location: York, United Kingdom |
Senior Member |
|
|
Hi Héctor,
In UML 2.1,, the endType and relatedElement features of Assocation have
a lowerbound of 1, signifying that a value is required, when
instantiating a valid UML model.
We are now enforcing this constraint with HUTN, so you'll need to update
your HUTN source files accordingly.
We don't have any plans to change this, but let us know if you find it
too restrictive - we'll consider your feedback carefully.
Cheers,
Louis.
Héctor Iturria wrote:
> Hi,
>
> As you have said, it has solved my problems except for the references.
> Do I really need to change the hutn files and add the information or is
> something that is going to be fixed too?
>
> For example, in associations I still have to specify the endType and
> relatedElement, before I had not.
>
> Many thanks,
> Héctor Iturria
>
|
|
| |
Re: [Epsilon] Default values in HUTN [message #561038 is a reply to message #900] |
Wed, 15 October 2008 17:55 |
Dimitrios Kolovos Messages: 1776 Registered: July 2009 |
Senior Member |
|
|
Hi Hector,
This happens because relatedElement and endType are both derived (and
thus unsettable references). I've updated the validation module to
handle such cases and committed the changes to the SVN. Now saving your
HUTN file should bring up 3 errors:
1) Association1 must specify a value for the following reference
features: memberEnd (as memberEnd has a lower-bound of 2)
2) Feature endType is not changeable
3) Feature relatedElement is not changeable
Thanks a lot for reporting this!
Cheers,
Dimitrios
Héctor Iturria wrote:
> Hi,
>
> It is not too much restrictive, but I was adding the definition of the
> properties in the HUTN files and I got some errors. I get no errors when
> coding, just when I save the file to generate the model.
>
> The error:
>
> org.eclipse.epsilon.hutn.exceptions.HutnGenerationException: Internal
> error: java.lang.UnsupportedOperationException
>
> raises from the property endType or relatedElement of an Association
> element.
>
> I send you a HUTN file and the console output.
>
> Many thanks,
> Héctor Iturria
>
>
>
>
> Louis Rose escribió:
>> Hi Héctor,
>>
>> In UML 2.1,, the endType and relatedElement features of Assocation
>> have a lowerbound of 1, signifying that a value is required, when
>> instantiating a valid UML model.
>>
>> We are now enforcing this constraint with HUTN, so you'll need to
>> update your HUTN source files accordingly.
>>
>> We don't have any plans to change this, but let us know if you find it
>> too restrictive - we'll consider your feedback carefully.
>>
>> Cheers,
>> Louis.
>>
>> Héctor Iturria wrote:
>>> Hi,
>>>
>>> As you have said, it has solved my problems except for the
>>> references. Do I really need to change the hutn files and add the
>>> information or is something that is going to be fixed too?
>>>
>>> For example, in associations I still have to specify the endType and
>>> relatedElement, before I had not.
>>>
>>> Many thanks,
>>> Héctor Iturria
>>>
>
|
|
| |
Re: [Epsilon] Default values in HUTN [message #561065 is a reply to message #958] |
Thu, 16 October 2008 08:24 |
Dimitrios Kolovos Messages: 1776 Registered: July 2009 |
Senior Member |
|
|
Hi Hector,
Thanks (again) for reporting this! Should be fixed now :)
Cheers,
Dimitrios
Héctor Iturria wrote:
> Hi!
>
> I got the 3 errors and I have already updated all my models. I am almost
> there...but not yet :)
>
> Now what it raises an error are enumerations. For example, in one of my
> HUTN files (based on the UML 2.1 metamodel) I have this fragment of code:
>
> Property "dst"{
> name: "dst"
> type: Class "Class2"
> aggregation: composite
> upper: 1
> }
>
> I have followed the example of your blog to specify the property
> aggregation, but I don't know if it is really a bug or I missed something.
>
> Again, I attach the output with the info of the error.
>
>
> Many thanks!
> Héctor Iturria
>
>
> Dimitrios Kolovos escribió:
>> Hi Hector,
>>
>> This happens because relatedElement and endType are both derived (and
>> thus unsettable references). I've updated the validation module to
>> handle such cases and committed the changes to the SVN. Now saving
>> your HUTN file should bring up 3 errors:
>>
>> 1) Association1 must specify a value for the following reference
>> features: memberEnd (as memberEnd has a lower-bound of 2)
>>
>> 2) Feature endType is not changeable
>> 3) Feature relatedElement is not changeable
>>
>> Thanks a lot for reporting this!
>>
>> Cheers,
>> Dimitrios
>>
>> Héctor Iturria wrote:
>>> Hi,
>>>
>>> It is not too much restrictive, but I was adding the definition of
>>> the properties in the HUTN files and I got some errors. I get no
>>> errors when coding, just when I save the file to generate the model.
>>>
>>> The error:
>>>
>>> org.eclipse.epsilon.hutn.exceptions.HutnGenerationException: Internal
>>> error: java.lang.UnsupportedOperationException
>>>
>>> raises from the property endType or relatedElement of an Association
>>> element.
>>>
>>> I send you a HUTN file and the console output.
>>>
>>> Many thanks,
>>> Héctor Iturria
>>>
>>>
>>>
>>>
>>> Louis Rose escribió:
>>>> Hi Héctor,
>>>>
>>>> In UML 2.1,, the endType and relatedElement features of Assocation
>>>> have a lowerbound of 1, signifying that a value is required, when
>>>> instantiating a valid UML model.
>>>>
>>>> We are now enforcing this constraint with HUTN, so you'll need to
>>>> update your HUTN source files accordingly.
>>>>
>>>> We don't have any plans to change this, but let us know if you find
>>>> it too restrictive - we'll consider your feedback carefully.
>>>>
>>>> Cheers,
>>>> Louis.
>>>>
>>>> Héctor Iturria wrote:
>>>>> Hi,
>>>>>
>>>>> As you have said, it has solved my problems except for the
>>>>> references. Do I really need to change the hutn files and add the
>>>>> information or is something that is going to be fixed too?
>>>>>
>>>>> For example, in associations I still have to specify the endType
>>>>> and relatedElement, before I had not.
>>>>>
>>>>> Many thanks,
>>>>> Héctor Iturria
>>>>>
>>>
>
|
|
|
Goto Forum:
Current Time: Wed Sep 25 23:43:59 GMT 2024
Powered by FUDForum. Page generated in 0.04663 seconds
|