Eclipse Community Forums: UML2 » UML2 3.0.0 metamodel now has unnamed associations

Help

Home

Home » Modeling » UML2 » UML2 3.0.0 metamodel now has unnamed associations

Show: Today's Messages :: Show Polls :: Message Navigator

UML2 3.0.0 metamodel now has unnamed associations [message #477814]

Sat, 11 October 2008 16:56

Eclipse User

Originally posted by: cdamus.zeligsoft.com

Hi,

In adopting the UML2 3.0.0 changes in the OCL project, I tripped across
a difference from the patch on Bug 232332 that I had previously tested.

There are now assocations in the UML.metamodel.uml model, such as the
new DecisionNode::decisionInputFlow, that are unnamed. Previously,
these would have (I assumed computed) names like
"A_decisionInputFlow_decisionNode."

Is this a bug? I clearly had a bug in the OCL parser, that would NPE on
these in the syntax-completion algorithm, but I am thinking that
probably these new associations should be consistent with all those that
came before.

Thanks,

Christian

Report message to a moderator

Re: UML2 3.0.0 metamodel now has unnamed associations [message #477820 is a reply to message #477814]

Tue, 14 October 2008 14:46

james bruck

Messages: 1724
Registered: July 2009

Senior Member

Hi Christian,

I will look into this today.

Cheers,
- James.

"Christian W. Damus" <cdamus@zeligsoft.com> wrote in message
news:gcqlsr$nrg$1@build.eclipse.org...
> Hi,
>
> In adopting the UML2 3.0.0 changes in the OCL project, I tripped across a
> difference from the patch on Bug 232332 that I had previously tested.
>
> There are now assocations in the UML.metamodel.uml model, such as the new
> DecisionNode::decisionInputFlow, that are unnamed. Previously, these
> would have (I assumed computed) names like
> "A_decisionInputFlow_decisionNode."
>
> Is this a bug? I clearly had a bug in the OCL parser, that would NPE on
> these in the syntax-completion algorithm, but I am thinking that probably
> these new associations should be consistent with all those that came
> before.
>
> Thanks,
>
> Christian

Report message to a moderator

Re: UML2 3.0.0 metamodel now has unnamed associations [message #477821 is a reply to message #477820]

Tue, 14 October 2008 17:00

Eclipse User

Originally posted by: cdamus.zeligsoft.com

Thanks, James,

I took a closer look at the UML metamodel using the OCL console:

Evaluating:
Association.allInstances()->select(name.oclIsUndefined())

Results:
<Association> A_result_writeStructuralFeatureAction
<Association> A_result_clearStructuralFeatureAction
<Association> A_object_startObjectBehaviorAction
<Association> A_decisionInputFlow_decisionNode

As you can see, there are four null-named associations. The label
provider kindly computes names for us.

Cheers,

Christian

James Bruck wrote:
> Hi Christian,
>
> I will look into this today.
>
> Cheers,
> - James.
>
>
>
> "Christian W. Damus" <cdamus@zeligsoft.com> wrote in message
> news:gcqlsr$nrg$1@build.eclipse.org...
>> Hi,
>>
>> In adopting the UML2 3.0.0 changes in the OCL project, I tripped across a
>> difference from the patch on Bug 232332 that I had previously tested.
>>
>> There are now assocations in the UML.metamodel.uml model, such as the new
>> DecisionNode::decisionInputFlow, that are unnamed. Previously, these
>> would have (I assumed computed) names like
>> "A_decisionInputFlow_decisionNode."
>>
>> Is this a bug? I clearly had a bug in the OCL parser, that would NPE on
>> these in the syntax-completion algorithm, but I am thinking that probably
>> these new associations should be consistent with all those that came
>> before.
>>
>> Thanks,
>>
>> Christian
>
>

Report message to a moderator

Re: UML2 3.0.0 metamodel now has unnamed associations [message #477822 is a reply to message #477820]

Tue, 14 October 2008 17:30

james bruck

Messages: 1724
Registered: July 2009

Senior Member

Hi Christian

The 4 offending associations can be tracked back to the original
Superstructure.uml. These are their id's

_0TsdIBk7Ed2AFo75-uQLRQ

_OPUWUCG7Ed2y9aVPK_72RA

_ijq7oBk8Ed2AFo75-uQLRQ

_wv1fYBk8Ed2AFo75-uQLRQ

That correspond to:

<Association> A_result_writeStructuralFeatureAction
<Association> A_result_clearStructuralFeatureAction
<Association> A_object_startObjectBehaviorAction
<Association> A_decisionInputFlow_decisionNode

I will update and regenerate.

Thanks for finding those missing names.

Cheers,

- James.

"James Bruck" <jbruck@ca.ibm.com> wrote in message
news:gd2b9p$ohs$1@build.eclipse.org...
> Hi Christian,
>
> I will look into this today.
>
> Cheers,
> - James.
>
>
>
> "Christian W. Damus" <cdamus@zeligsoft.com> wrote in message
> news:gcqlsr$nrg$1@build.eclipse.org...
>> Hi,
>>
>> In adopting the UML2 3.0.0 changes in the OCL project, I tripped across a
>> difference from the patch on Bug 232332 that I had previously tested.
>>
>> There are now assocations in the UML.metamodel.uml model, such as the new
>> DecisionNode::decisionInputFlow, that are unnamed. Previously, these
>> would have (I assumed computed) names like
>> "A_decisionInputFlow_decisionNode."
>>
>> Is this a bug? I clearly had a bug in the OCL parser, that would NPE on
>> these in the syntax-completion algorithm, but I am thinking that probably
>> these new associations should be consistent with all those that came
>> before.
>>
>> Thanks,
>>
>> Christian
>
>

Report message to a moderator