| ETL - How to Handle Metamodel Extensions [message #659732] |
Tue, 15 March 2011 08:10  |
Eclipse User |
|
|
|
Hi Dimitris,
I have a metamodel with a containment called extensions of type = meta-class 'AbstractExtension'
AbstractExtension can be extended in new metamodels to extend the modelling notation.
I have recently changed to use Helios and this version of Epsilon: 0.9.0.201101251228
The problem is that my ETL rules no longer trigger when source is a metaclass of the new extension metamodel.
e.g. Neither of these rules are triggered...
rule test
transform s : Source!NewMetaClass
to t : Target!OldMetaClass{
"TEST".println();
}
rule test2
transform s : SourceExtension!NewMetaClass
to t : Target!OldMetaClass{
"TEST".println();
}
Where NewMetaClass extends AbstractExtension.
Source is the source model with the old Metamodel
SourceExtension is the same source model with the new extension metamodel.
By the way, if you type NewMetaClass incorrectly it gives an exception so it is finding this metaclass.
Also, the following finds an instance of the new metaclass...
@greedy
rule test
transform s : Source!AbstractExtension
to t : Target!NewMetaClass{
"TEST".println();
s.name.println();
}
The same rules used to work ok in the old Galileo version of Epsilon 0.8.9.201004151115
Has something changed? Am I doing something wrong?
Regards
Asieh
|
|
|
|
Powered by
FUDForum. Page generated in 0.02947 seconds
Home