|Re: [QVTo] trace model and proxies [message #946608 is a reply to message #946596]
||Tue, 16 October 2012 10:37
| Ed Willink
Registered: July 2009
[You may find that your problem is the same as in the "Resolve EValues
from a qvtotrace file" thread.]
Getting UML declarations right was hard. The advent of UML 2.4 support
made it nigh on impossible, so UMLResourcesUtil.init was added.
You give no indication of what tools or versions you are using, no
reproducible code, and no indication of what intervening activities
cause your intermittency. I suspect something is adjusting a global
registry since these problems are almost always related to Resource
I'm afraid that I will not be able to give you any further help without
a zipped project including a launch configuration that can just be
installed and run to demonstrate your problem.
On 16/10/2012 11:20, nicholas pacini wrote:
> hello all,
> I have found a strange behavior regarding the operational QVT trace
> model. Maybe someone can help me understanding this issue.
> I'm using the Java API of the QVTo Trace to get some information about
> the result of a UML to UML transformation written in QVTo (btw, not
> written by me). With different UML models i have different behaviors
> regarding proxies.
> For example if a get the model element from the context of a trace
> EObject elem =
> sometimes i get elem as a proxy, sometimes not. I've checked with
> elem.eIsProxy() and, in the case it is a proxy, i'm unable to resolve it.
> do you have any idea regarding this issue and/or any advice?
Powered by FUDForum
. Page generated in 0.02016 seconds