| Re: [m2t-dev] [Acceleo] Generation of code and creation of sub-unit of model remove stereotypes in the sub-unit of model |
|
Dear all, Thanks to Camille I could resolve partially my problem with uml profiles and proxies but I still have issues regarding Acceleo. I added the uml2 extension that references the profiles according to the pathmap:
</extension>
<extension
point="org.eclipse.uml2.uml.dynamic_package">
<profile
uri="http://www.spacebel.com/profiles/functional_C"
location="pathmap://SPACEBEL_PROFILES/Functional_C/functional_C.profile.uml#_xzXxYEr9EeS32Jy9pwljCQ"/> </extension> The last remaining problem happens when I generate code by using Acceleo (the code is correctly generated) and the uml model (decomposed in several sub-units). The stereotypes of the sub-units don’t appear anymore
in the UML editor. In order to recover them, I need to restart Eclipse. In addition, my Acceleo generator causes the following issue in Papyrus (DHS.uml is a sub-unit of SPB_OBSW.uml):
Does Acceleo break anything around UML package registry ? Best regards, Johan From: Johan Hardy
Dear all, I decided to send a mail to m2t dev-list because I experienced a strange behavior between Papyrus 1.0.1 or the simple UML Editor & Acceleo 5.4.0. The issue was originally reported to Papyrus MDT project but it seems to be linked to Acceleo
or UML: https://bugs.eclipse.org/bugs/show_bug.cgi?id=445473 The description of the problem is in the title. I have a big model (where a profile is applied) with a lot of packages which contains classes where lots of stereotypes are applied. FYI, the applied profile is enclosed in a plugin with EMF
& papyrus extensions. <extension point="org.eclipse.emf.ecore.uri_mapping"> <mapping source="pathmap://resources/Functional_C/" target="platform:/plugin/com.spacebel.papyrus.profile.functional_C/resources/Functional_C/"> </mapping> </extension> <extension point="org.eclipse.papyrus.uml.extensionpoints.UMLProfile"> <profile description="UML profile for functional C" iconpath="icons/Profile.gif" name="Functional C" path="pathmap://resources/Functional_C/functional_C.profile.uml" provider="Spacebel SA"> </profile> </extension> When I create a sub-unit for a package (for example team collaboration), all the stereotypes applied on the people below are still applied and I can continue to model my software
J .. No problem. Then, when I decide to generate my code by using my own UML to C generator, there is no problem too. However … when I close the model after the generation and I reopen the model again, the applied stereotypes have disappeared in the sub-unit …
L. To sum-up: -Own Acceleo generator UML to C enclosed in a plugin -Own profile enclosed in a plugin 1.
Open uml model (whatever it is papyrus or the simple UML Editor it is the same issue) 2.
Creation of model sub-units 3.
UML Modeling 4.
Generation of the code by using Acceleo -> code is fine 5.
Close the uml model 6.
Reopen the uml model again 7.
The stereotypes applied on the sub-unit elements disappeared Does anyone already experience that behavior ? Do you know what I miss ? In advance thanks for any proposition ! Best regards;
------------------------------------------------------------------------------ E-MAIL DISCLAIMER The present message may contain confidential and/or legally privileged information. If you are not the intended addressee and in case of a transmission error, please notify the sender immediately and destroy this E-mail. Disclosure, reproduction or distribution of this document and its possible attachments is strictly forbidden. SPACEBEL denies all liability for incomplete, improper, inaccurate, intercepted, (partly) destroyed, lost and/or belated transmission of the current information given that unencrypted electronic transmission cannot currently be guaranteed to be secure or error free. Upon request or in conformity with formal, contractual agreements, an originally signed hard copy will be sent to you to confirm the information contained in this E-mail. SPACEBEL denies all liability where E-mail is used for private use. SPACEBEL cannot be held responsible for possible viruses that might corrupt this message and/or your computer system. ------------------------------------------------------------------------------- |
