Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [viatra-dev] Transformation API
So the line

basic.set(state_Name, p.name)///name = p.name

from http://wiki.eclipse.org/VIATRA2/EMF/Transformation_API#Defining_rules.2C_rulegroups is bogus?


Why don't we require to use the EMF reflective API in this case? I.e. by passing the appropriate literal from the EPackage?

--
Istvan RATH, PhD
Research fellow
Budapest University of Technology and Economics
Fault Tolerant Systems Research Group

On Sunday, September 29, 2013 at 9:41 PM, Ujhelyi Zoltán wrote:

The problem is that I cannot find any implementation behind the interface, that works, as the method.name would return a string without any metainformation, e.g. the corresponding EStructuralFeature. Without knowing the feature (even by knowing the defining object and the Java type) it is not possible to change to original reference.

This issue does not appear in case of lists, as EMF always returns modifiable lists.

Zoli
-- Zoltán Ujhelyi

Fault Tolerant Systems Research Group
Budapest University of Technology and Economics

On 2013.09.29., at 21:36, Istvan Rath <rath@xxxxxxxxxx> wrote:


Gábor suggested to have convenience methods that handle ELists findable from the EMF API, e.g.:
* method.add(method.parameters, newParameter)

This approach works well for multi-valued references (even better than my EMF-reflective implementation), however, for single-value references or attribute I see no way of implementing an API like this, e.g.:
* method.set(method.name (http://method.name), "main")


What's wrong with this? I don't think it looks awkward.

--
Istvan RATH, PhD
Research fellow
Budapest University of Technology and Economics
Fault Tolerant Systems Research Group

_______________________________________________
viatra-dev mailing list

_______________________________________________
viatra-dev mailing list

Back to the top