Eclipse Community Forums: ATL » [ATL] Containment references cannot span across models

Home » Modeling » ATL » [ATL] Containment references cannot span across models(Meta-model in split in two ecore files.)

Show: Today's Messages :: Show Polls :: Message Navigator

[ATL] Containment references cannot span across models [message #989468]

Thu, 06 December 2012 10:46

Leonid Ripeynih

Messages: 150
Registered: February 2012

Senior Member

Hi!

I've run into a problem using ATL:

I have a source meta-model (UML), and my target meta-model. Meta model is basically split into two: a common part, used by other models, and one of the concrete models.

Here is failing rule.

lazy rule createConetnt {
	from
		clazz: UML!Class
	to
		ds: Desc!ContentElem (
			table1 <- thisModule.contentTable(clazz.name),
			nestedFieldset <- thisModule.createNestedFieldSet(clazz),
			table <- UML!Association.allInstances() -> select(
				acc | acc.endType.first().name.endsWith(clazz.name)
			)
		)
}

rule createTableFromAssociation {
	from
		ass: UML!Association
	to
		table: FieldSet!TableElem (
			id <- ass.endType.first().name,
			desc <- ass.endType.first().name,
			type <- ass.endType.first().name
		)
}

It's falinig setting table with:

Cannot set feature table to value [org.eclipse.emf.ecore.impl.DynamicEObjectImpl@4a31a39e (eClass: org.eclipse.emf.ecore.impl.EClassImpl@7cf1f9d3 (name: TableElem) (instanceClassName: null) (abstract: false, interface: false))], containment references cannot span across models.

Both nestedFieldset and table feature type belongs to the 'common' metamodel. Is there any way to solve it? I hope it's a common problem, becouse keeping everything in one (very) doesn't looks like very good idea. Thanks in advance.

Report message to a moderator

Re: [ATL] Containment references cannot span across models [message #989491 is a reply to message #989468]

Thu, 06 December 2012 13:30

Hugo Bruneliere

Messages: 674
Registered: July 2009

Senior Member

Hello,

When you run your ATL transformation (via a launch configuration or programmatically), do you set the "Allow inter-model references" parameter to true?
If no, this could be a potential source for your issue.

Best regards,

Hugo

--------------------------------------------------------
Hugo Bruneliere, PhD
NaoMod team (IMT Atlantique & LS2N-CNRS)
Nantes - France
--------------------------------------------------------

Report message to a moderator

Re: [ATL] Containment references cannot span across models [message #989514 is a reply to message #989491]

Thu, 06 December 2012 14:57

Leonid Ripeynih

Messages: 150
Registered: February 2012

Senior Member

Yes, I've set it.

Report message to a moderator

Re: [ATL] Containment references cannot span across models [message #989546 is a reply to message #989514]

Thu, 06 December 2012 16:53

Hugo Bruneliere

Messages: 674
Registered: July 2009

Senior Member

In ATL, you can set references between elements from different models as long as these references are not containment references.
In your case, the Desc!ContentElem element actually contains FieldSet!TableElem elements via the table reference. So these two types of elements cannot be in different models.
If the table reference was not a containment reference, this should work.

Hugo

--------------------------------------------------------
Hugo Bruneliere, PhD
NaoMod team (IMT Atlantique & LS2N-CNRS)
Nantes - France
--------------------------------------------------------

Report message to a moderator

Re: [ATL] Containment references cannot span across models [message #989556 is a reply to message #989546]

Thu, 06 December 2012 17:38

Leonid Ripeynih

Messages: 150
Registered: February 2012

Senior Member

Let me clarify a bit. It's meta models are split, not the models, In fact, in normal (de)serrializaion they're put together:

<content>
 <table id="some_id">
 ...
</content>

I have solved this issue by removing references to FieldSet and just writing

Desc!TableElem

What's interesting, ATL IDE itself detects (in popup) the table type as Desc!TableElem (as Desc meta-model referencing FieldSet meta-model). But, here is still little problem: i have no context assis for that Desc![FieldSetFeatures].

Can you help me understand, what's going on?

Report message to a moderator

Re: [ATL] Containment references cannot span across models [message #989667 is a reply to message #989556]

Fri, 07 December 2012 09:06

Hugo Bruneliere

Messages: 674
Registered: July 2009

Senior Member

What do you mean by Desc![FieldSetFeatures]? Is it another type of element from your metamodel?

Hugo

--------------------------------------------------------
Hugo Bruneliere, PhD
NaoMod team (IMT Atlantique & LS2N-CNRS)
Nantes - France
--------------------------------------------------------

Report message to a moderator

Re: [ATL] Containment references cannot span across models [message #989837 is a reply to message #989667]

Sat, 08 December 2012 07:18

Leonid Ripeynih

Messages: 150
Registered: February 2012

Senior Member

No.

Desc meta-model is referensing FieldSet meta-model. So, I just meant Desc! and then feature names from FieldSet meta model. Like, Desc!NestedFieldSet, having NestedFieldSet actually defined in FieldSet meta-model.

Report message to a moderator

Re: [ATL] Containment references cannot span across models [message #989963 is a reply to message #989837]

Mon, 10 December 2012 09:42

Hugo Bruneliere

Messages: 674
Registered: July 2009

Senior Member

Hello,

Thus it seems that the current content assist version does not support auto-completion for elements coming from indirectly referred metamodels.
You could raise an ATL bug to keep track of this.

Hugo

--------------------------------------------------------
Hugo Bruneliere, PhD
NaoMod team (IMT Atlantique & LS2N-CNRS)
Nantes - France
--------------------------------------------------------

Report message to a moderator

Previous Topic:	Stack size limitation in EMF-specific VM
Next Topic:	missing metdamodel

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 18 17:33:04 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter