Aggregation end not generated in code

[ylaporte]

The following issue seems like a bug:

ClassA<><------------->ClassB

In a situation where I have a shared aggregation (the behavior is the same with composite aggregations) with navigation in both directions. Independently of role names and multiplicity, ClassA contains the reference to class B but ClassB doesn't contain the reference to ClassA. Also, if ClassA resides in a diferent package, the import statement for the class is generated, but still not the attribute in the ClassB.

[Eve]

Correct, EA intentionally only generates the attribute for the aggregate member, never the reference to the owner.

[ylaporte]

Mhh.. not a good surprise, I would have expected the generation of attributes to be determined by navigability.

We're migrating a model from Rose and the code form that model is regenerated regularly. This really complicates things.

What is the usual way to weight in on a change of the software?

[Geert Bellekens]

Send in a feature request (use the link on the bottom of the page)

And then... go to church and burn some candles :-/ (or similar depending on your religion)

Geert