|
[
Permlink
| « Hide
]
Christian Groove added a comment - 15/Sep/08 10:20 PM
here is a screenshop of the assoc class
Hello Christian,
you can configure the columns of a n:m relationship by configure the association ends of the association. Declare the ends as <<Field>> and customize the 'columnName' tagged value. The link-table of the relation can be customized by setting the 'coll_table' tagged value of the <<EntityRelation>> AssociationClasses are not used. Are there any other questions regarding this issue? Regards Darius Salut Darius,
thanks for your immediate reply. Ok, i'll try you suggested solution. Anyway, do you belive, that fornax will support for this UML 2.1 feature, someday (or in 0.7.1). Personnally, i would favour any graphical means supported by UML2 over any helping workaround by stereotype-attributes, because the later behaves like additional information medium for artefacts, that can not be expressed in UML. But finally, association-link does describe n:m relationsships as best as possible. Do you belive, that this could be an argument, to support these artefacts ? Thanx for you help!!!! Groovy Hello Christian,
you are right that the modelling of bidirectional associations work very well with association ends. But in the past this constrict was not supported by every uml2 modeling tool. Therefore we desided to use stereotypes. Now we have the (problem), that a solution is already implemented and used by others. Therefore I think, this behavior should not be changed. Regards Darius PS: In addition to that the navigation in an associationclass is complette different from associations, as I can see from the errors thrown by the workflow. This would cause complete new templates and extensions. Salut Darius,
? Now we have the (problem), that a solution is already implemented and used by others Just for fun i loaded a 2.1.0 Diagram with association classes into an old 1.3.0 Topcased tool. The funny think was: it was loaded corrector, but the presentation of the diagramm was a little bit messed up. The answer to this behaviour is quite simple. Loading and Datarepresentation is done by a sparate UML projekt/componenten, that is also shipped with Eclipse. Not surprisingly, some of the relation-ship attributes were set correctly. Do you really thing that assoc classes looks so different like navigations ? (continued..)
.... What will you do, when Topcase 2.x will support for (UML: n-ary association) ? A+ Groovy Hello Christian,
first of all the cartridge is (should be) independent of any modelling tool. Of cause, there are tools with different interpretations of the UML2 standard. Also different version of the same tool handle things different. Also there are different ways to express concepts of your domain (DSL). In our case we desided to model an n:m reference by an association. Additional informations are placed into tagged values. Changing this behavior would change the DSL. This imply a braking change. Quote Christian: Just for fun i loaded a 2.1.0 Diagram with association classes into an old 1.3.0 Topcased tool. I started with the 0.9.0 release of topcased :-) Quote: What will you do, when Topcase 2.x will support for (UML: n-ary association) ? Then we have a problem. But we can deside that the Fornax Hibernate Cartridge DSL forbit to draw associations with more then two ends. The only way to integrate AssociationClasses is that this would be an alternative way to model bidirectional n:m references. If you would provide a solution, I could build in this functionality. Regards Darius Salut Darius,
> you can configure the columns of a n:m relationship by configure the association ends of the association. > Declare the ends as <<Field>> and customize the 'columnName' tagged value. In this case Topcased user would habe to select the association-link and assign one(!) column - name for both relational-attributes in both entity-classes. Am i right ? Groovy Salut Darius,
i testet now your solution ... > The link-table of the relation can be customized by setting the 'coll_table' tagged value of the <<EntityRelation>> In topcase i can not find the "coll_table", there is only a "coll table name" that is irgnored by fornax. Groovy Hallo Christian,
maybe the attatched figure illustrate the configuration. > In this case Topcased user No, not only Topcased users. All users should model in the same way. Hello,
> In topcase i can not find the "coll_table", there is only a "coll table name" that is irgnored by fornax. In this cause you discovered a bug. I will have a closer look at this. The reference model is modeled with MagicDraw. The tests for Topcased models are very rudimental. Regards The tagged value for configure the tabble name of an bidirectional n:m association is 'coll_tableName'
This tagged value can be used to set the table, if a collection should be mapped. Please close this issue is everything work correct and reopen if the problem still exists. Regards Darius Salut Darius,
iff your profile will not support for a coll_tableName, i can not selecct it out of my Topcased! As i mentioned before, i can set a "coll table name", but this one is not recognized by your transforming tool! Simply saying: I can not use coll_tableName cause i can not see it. I can only set "coll table name" !!!! Thanks Groovy |
||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
Parser does not provide for Associatan Class between two entity classes.
