|Re: ATL does not resolve proxies into another model [message #517576 is a reply to message #517564]
||Mon, 01 March 2010 06:26
| Ed Merks
Registered: July 2009
The most common reason for proxies failing to resolve loading the
resource with a URI that isn't absolute, i.e., isn't one that starts
with a scheme/protocol. Relative references within a resource need to
be resolved against the URI of the containing resource and URI
resolution is only defined for resolving a relative URI against an
absolute URI. Be sure you're using something like
> Hello Community,
> I try to transform a model element, which has a reference into another
> model. When I try to access this reference, ATL tells me oclUndefined.
> I loaded also the other model in the ATL Transformation but it still
> does not work.
> In the picture you see how the metamodels are defined.
> There is one metamodel core, containing a Resource and a Scenario.
> Another metamodel Parameter containing a Step.
> Then there are metamodels MDBPECompanyCore refining Resource and two
> metamodels MDBPECompanyParameter and MDBPEDepartmentParameter refining
> I have three models.
> One Model contains the Company and a Scenario.
> Another Model contains the Element WorkingTimeDemand from the
> Metamodel MDBPECompanyParameter and a reference to the Scenario in the
> first Model through "relatedScenario".
> A third Model should be created with the transformation.
> When I load the first and the second model into the ATL Transformation
> and try to access the Scenario form WorkingTimeDemand through
> "relatedScenario" the Reference cannot be resolved. The debug
> information of ATL tells me that "relatedScenario" is from type
> "<unknown>!<unnamed>:MDBPEDepartmentParameter!Scenario" which looks
> like, ATL try to locate the Scenario in themetamodel of
> Any ideas, why ATL cannot resolve the reference?
> Thanks Simon
Powered by FUDForum
. Page generated in 0.01653 seconds