| [ATL] About internal traceability links in ATL [message #643270] |
Mon, 06 December 2010 05:33  |
Eclipse User |
|
|
|
Hi all,
after reading "Loosely Coupled Traceability for ATL" written by Frédéric
Jouault I have a question about the internal traceability links in ATL.
That paper states that internal traceability links in ATL are links
labelled with the rule name and targetting the input and output element.
If that's true, I wonder how the resolveTemp() operation works, because
that expects the name of the output pattern variable and not the rule
name. So I guess that (at least nowadays) the internal traceability
links are triples of the form (outputPatternVarName, sourceObject,
targetObject). Is that correct?
Bye,
Tassilo
--
Dipl.-Inform. Tassilo Horn | Room: B015
University of Koblenz-Landau, Campus Koblenz | Phone: +49 (261) 287-2745
Institute for Software Technology | Mail: horn@uni-koblenz.de
Universitätsstr. 1, 56070 Koblenz, Germany |
|
|
|
|
| Re: [ATL] About internal traceability links in ATL [message #643278 is a reply to message #643271] |
Mon, 06 December 2010 06:26  |
| Eclipse User |
|
|
|
Sylvain EVEILLARD <s.eveillard@netfective.com> writes:
Hi Sylvain,
> I'd suggest you to have a look at the TransientLink and
> TransientLinkSet classes in org.eclipse.m2m.atl.engine.emfvm.lib.
According to
http://ftp.kaist.ac.kr/eclipse/modeling/m2m/atl/javadoc/3.2. 0/org/eclipse/m2m/atl/engine/emfvm/lib/TransientLink.html
(that's the most current API docs I could find), it's an undocumented
feature. :-)
Fun aside: I can see that indeed the rule name can be stored with a
link, and both source as well target elements are referenced in terms of
Maps, but since the Maps are from Object to Object, it's not easy to
reason about their contents...
Bye,
Tassilo
--
Dipl.-Inform. Tassilo Horn | Room: B015
University of Koblenz-Landau, Campus Koblenz | Phone: +49 (261) 287-2745
Institute for Software Technology | Mail: horn@uni-koblenz.de
Universitätsstr. 1, 56070 Koblenz, Germany |
|
|
|
Powered by
FUDForum. Page generated in 0.46904 seconds
Home