[ http://jira.andromda.org/browse/UMLMETA-28?page=all ]
Wouter Zoons updated UMLMETA-28:
--------------------------------
Comment: was deleted
> MagicDraw not generating UML:AssociationClass information workaround
> proposition
> --------------------------------------------------------------------------------
>
> Key: UMLMETA-28
> URL: http://jira.andromda.org/browse/UMLMETA-28
> Project: UML Metafacades
> Type: New Feature
> Versions: 3.0 RC1
> Environment: MagicDraw 9, UML 1.4, XMI 1.2, XSLT 1.0
> Reporter: Cédric Vidal
> Assignee: Wouter Zoons
> Attachments: Identity.xsl, MagicDrawAssociationClassNormalizer.xsl
>
> The UML 1.4 model allows you to create a class for representing an existing
> association (in the visualization it is a dashed line between the association
> and the related class) which in XMI 1.2 must be generated as a matching
> UML:AssociationClass meta information (Poseidon does that well though it does
> not allow association classes to be specialized).
> MagicDraw allows you to draw the forementionned dashed line in a diagram, but
> it does not generate properly the matching UML:AssociationClass meta
> informations in any of its XMI outputs. The association class is generated as
> a normal UML:Class and the dashed line diagram information is only generated
> using the XMI.extensions mecanism.
> The MagicDraw generated XMI lacking UML:AssociationClass meta informations,
> AndroMDA has no way to know that there is actually an association class. So
> here is a XSLT stylesheet that takes as input a MagicDraw generated XMI 1.2
> file, fetches the graphical dashed line information, the participating
> UML:Class and UML:Association and merges them into a UML:AssociationClass
> generating a XMI file that AndroMDA can understand.
> Known limitations:
> - as the information used as input is partly graphical, the diagrams must be
> thought with care.
> - if two distinct diagrams draw a dashed line between a given association and
> a given class, the XSLT behavior is unknown: so draw only one diagram with
> the dashed line to be sure. Support for duplicates removal might be added in
> the future.
> - this is a hack, proper UML:AssociationClass support seems to be scheduled
> for MagicDraw 10.
> - don't even try to load the resulting XMI file in any UML Editor, it is
> likely to fail, the resulting XMI is only meant to be loaded by AndroMDA. A
> sufficient evidence is that the XSLT creates a UML:AssociationClass out of a
> UML:Class and a UML:Association, so the fact that the UML:Class was actually
> a UML:Class is lost in the output.
> - consider the XSLT output only as an temporary file fed to AndroMDA.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
