Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - tinue

Pages: [1]
General Board / Report: How include attributes of diagram elemens?
« on: October 27, 2011, 09:47:51 pm »
In a report, I'd like to include the attributes of objects in a diagram. How can I do this?
  • The "Element" tag doesn't work, because there are no elements (apart from the diagram itself: The objects are in another model).
  • The "Diagram"->"Element" tag doesn't work, because it has no "Attribute" child.
Is there another way?

Update: I learned from the documentation that there is another way, which in my case works partially: Leave the Element-Tag of the Diagram empty, and define the desired layout in the "Element" tag (which does have the "Attribute" child).

My problem with this approach is: I really need different layouts in the "Diagram->Elements" and in the "Elements" sections of my report. So this doesn't really solve my issue.

Thanks! Martin

General Board / Re: Attributes as Associations and vice versa
« on: May 26, 2011, 12:32:37 am »
Hello Geert

We have the same rule for service modeling: Only primitive types as attributes. Your hint of using a dependency on the diagram is helpful, thanks!

There is another quirk in our environment, though. The system holding the service definitions and the datatypes does not "speak" UML yet, and knows only attributes.

We are now developing an UML import/export feature, and now the problem hits: While exporting, we can decide on attribute vs. association based on the type, so no problem there.
What is lost though is the field order: When I re-import, there will be either attributes first, followed by associations, or vice-versa.

If I could mix them in the model, I could keep the field ordering intact.

Again, thanks and best regards,


General Board / Re: Attributes as Associations and vice versa
« on: May 18, 2011, 09:16:42 pm »
Submit a formal feature request using the links below...
Done, thanks for the hint!

Regards, Martin

General Board / Attributes as Associations and vice versa
« on: May 18, 2011, 06:14:01 am »
Fundamentally, any (directed) relationship between two classes can be shown on a diagram as an Association or as an Attribute of the source class.
For example, in a particular "Service Interface" (datatype) class diagram I want to explicitly display my Enumerations, so that I see their literals.
On this diagram, I need to display the relationship between the Datatype and the Enumeration in the form of an Association.
On another diagram, I might not be interested in such details, so I merely show the attribute of the class and can see the particular (Enumeration) type.

Therefore, I would like to decide on the level of a diagram whether I show an Association or a Relationship.

As far as I can see, I have to decide in the model itself whether there is an Attribute or a Relationship, so I can't do what I like to do.

Am I overlooking something, or is this simply not doable?

Thanks! Martin

Bugs and Issues / Re: Conflict with similar stereotypes
« on: November 16, 2012, 07:45:29 pm »
I turned off almost all MDG Technologies except the one I was using, and then it worked. It seems clear the the wrong stereotype is picked: "union" from the C or C++ package, instead of "Union" from my own. It seems to only fail when the stereotypes differ only in capitalization. If they are spelled exactly the same it seems to work.
Regards, Martin

Bugs and Issues / Conflict with similar stereotypes
« on: November 15, 2012, 11:27:59 pm »

We use a private MDG technology, which provides a Stereotype with tagged values called "Union". There is a "union" (small u) in "C" and one in "C++" as well.
When I explicitly select "our" Union, I get a "union" written into the object. "Synchronize Stereotype" does not work, because it apparently thinks its one of the other unions.
Other users with the exact same model do not have this issue, so it must be something outside of the model which is triggering this.
Does anyone have an idea where to look?
It happens in all EA Versions from 6.2 up to 6.3.5.

Bugs and Issues / RTF Report: Landscape no longer works
« on: May 10, 2012, 05:00:53 am »
I have a report template that has a page break in the middle, and after the page break the page orientation is landscape. Up and until 9.2 this was honored. With 9.3, the page after the page break remains in portrait mode (confirmed with the internal rtf viewer and with MS Word). The template still looks ok, i.e. I can see the landscape mode in the template editor. Just the generated output is wrong.
Can anybody confirm this?

Thanks! Martin

Pages: [1]