Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic Rhapsody (steve huntington)
Decrease font size
Increase font size
Topic Title: Association Classes
Topic Summary:
Created On: 11-May-2005 10:48
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 11-May-2005 10:48
User is offline View Users Profile Print this message


rikard Lindeby

Posts: 1
Joined: 27-May-2005

Does anyone know why there is no code generated for association classes? There is also no possibility to associate association classes with other classes, which is suppossed to be possible according to the UML2.0 superstructure document?
/Mattias via Rikard
Report this to a Moderator Report this to a Moderator
 17-May-2005 20:25
User is offline View Users Profile Print this message


Default User

Posts: 11
Joined: 25-Mar-2005

I believe Rhapsody only supports the graphical modeling of Association Classes but does not support the code generation. This might be possible in a future release.
Report this to a Moderator Report this to a Moderator
 5-Jan-2006 16:11
User is offline View Users Profile Print this message


Charlie Lane

Posts: 86
Joined: 16-Sep-2005

Just wondering whether the situation progressed during 2005?
Is there any planned release for association class code generation?
Has anyone found a reasonable way of using them?
Report this to a Moderator Report this to a Moderator
 29-Aug-2006 19:22
User is offline View Users Profile Print this message


Paul Coene

Posts: 10
Joined: 15-Dec-2005

I too have this question, over a year later.

Here's what I observe in Rhapsody 6.1:

If I create two classes and draw an association between them, and then add a 3rd class as an association class via the "anchor" graphic, Rhapsody does a whole bunch of magic. I find that the association is labeled with the name of the Association class, the new association class is REMOVED from the class list, and many new options show up on the association's features list. This looks like far too much activity for there not to be support?! I mean, the class is removed from the class list. This is way more than graphical support. Is there some new support in there that we need to know about? I'd really like to be able to use this construct so that two classes can share one container of a 3rd class.

Here's the picture of the OMD:

[IMG]http://72.148.31.226/images/omd.JPG[/IMG]

Here's a picture of the browser:

[IMG]http://72.148.31.226/images/browser.JPG[/IMG]

As you can see, Rhapsody has done alot with this, more than just a pretty picture. Is there any documentation on how to use this feature and how to generate code?

What I want, is both Customer and Vendor classes to have immediate accessor to a common container of Invoices.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic Rhapsody forum.
There are currently 1 users logged in.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.