|
| Re: [ATL] ATL transformation in a plugin involving profiles [message #772599 is a reply to message #772338] |
Fri, 30 December 2011 06:30   |
 Ed Willink
Messages: 7655
Registered: July 2009 |
Senior Member |
|
|
Hi
You are working in an area that has for a long time fallen into a gap
between the UML and OCL specifications; what does a profiled UML model
look like when used for OCL evaluation?
In the absence of any coherent OCL specification or implementation,
transformation tools have endeavoured to provide some support, sometimes
through reflective methods such as getAppliedStereotype(). These all
seem to ignore the problem that the run-time model should be the result
of profile application rather than the naked model with awkward appendages.
I suspect that the only way to get a useable profiled model today, is to
apply the profile in the UML Editor and then export the model to Ecore
so that all stereotypes have been applied and both you and ATL can see
what you're doing.
Regards
Ed Willink
On 29/12/2011 14:47, Alessandro Tiso wrote:
> Hi All,
>
> I have written a transformation from an UML model (that use a
> particular UML profile) and a model conform to a specific meta-model,
> to a model conform to a specific meta-model. In other words the
> transformation has two input models (the profiled UML model and
> another model) and one output model. Using the run configuration the
> output model is created as expected. After that I created an ATL
> plugin, first using the option available in eclipse Indigo, and then
> modifying the source generated to have a simple menu to activate the
> plugin. When I debug the plugin in a Eclipse application, seems that
> stereotypes in the input model are ignored.
> I have tried to add, as input, the profile model, without any
> differences in the output.
>
> Can someone help me?
>
> Thanks in advance
|
|
|
|
Powered by
FUDForum. Page generated in 0.01834 seconds
] 
Search
Help
Register
Login
Home
