RE: [Andromda-user] Association and Dependancy

[Matthias Bohlen]

Title: Nachricht

Hi Matthew,   I am not sure that I understand you correctly.   First of all, <<ejbref>> is an old stereotype that is not used any more. It is called <<EntityRef>>, now (see http://www.andromda.org/pages/modeling.html for a definitive list of stereotypes).   Second: A dependency with <<EntityRef>> cause an EJB reference generated by the EJB cartridge. For other cartridges, this stereotype is ignored. Dependencies without a stereotype simply generate a Java "import" statement.   Third: Associations between <<Entity>> classes do matter! They generate persistent relationships with getters/setters in the EJB as well as in the Hibernate cartridge.   Cheers... Matthias -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Pomar Sent: Thursday, July 03, 2003 2:43 PM To: [EMAIL PROTECTED] Subject: [Andromda-user] Association and Dependancy I noticed the car rental UML example uses both Associations and Dependancies to establish relationships between entities. Could some verify that only Dependancies marked with a stereotype of <<ejbref>> drive code generation and Associations do not matter for code generation in AndroMDA?   Thanks, Matthew Pomar