Code generation for Associations

[dserodio]

Can EA generate methods for associations, or only attributes?

[Eve]

Play around with the linked attribute templates.  You can generate a method if you want.

It won't synchronise though.

Simon

[dserodio]

Thanks for the tip, I created a "LinkedAttribute__Body" template and it works. I will post it to the forum later.

*But* it only works for "plain" associations, not with aggregation nor composition. Why is that? Is there any way around it?

Thanks again.

[da_Burp]

*But* it only works for "plain" associations, not with aggregation nor composition. Why is that? Is there any way around it?

It seems this behaviour is still the same in version 6.5.806. Even though I came across this behaviour during transformation and not generation it is identical. So a composition or aggregation won't result in a linked attribute. Is there any specific UML design reason why it is implemented like this?

I have a model here where a composition is bi-directional. But  because the composite side doesn't result in a Linked Attribute it's not really navigable. I've never see it in any model using this bi-directional composition, and I faintly remember reading something it's actually not appropriate, but i'm not sure about that. But I wonder what there would be against this.

[«Midnight»]

What about EA 7.0?

[da_Burp]

I could give that a try on another PC later on. If it works I will drive the version manager nuts though, Since we have the policy of sticking to a version for a little longer. This is because each update requires a new roll-out has to be arranged for the whole company.

[Eve]

The rules for what constitutes an attribute vary somewhat between associations without any aggregation and those that do.  However, LinkedAttribute templates should still execute for aggregations and compositions.  (They won't generate at the other end)

[da_Burp]

The rules for what constitutes an attribute vary somewhat between associations without any aggregation and those that do.  However, LinkedAttribute templates should still execute for aggregations and compositions.  (They won't generate at the other end)

And that axectly what i'm running up against now. So the only option is to have bot sides navigable is either make it a bi-directional association again or to add the attribute X manually on class B the PIM in the following situation: [A]<><-X---Y->?

[Eve]

Yes, either of those two options should work.

[«Midnight»]

Perhaps this would be a good thing to add to the properties dialog for connectors. The new tabbed dialogs would seem to support this well.

Just my 0.02 CAD worth...

David