[news.eclipse.modeling.gmt.amw] Re: ATL2Wtracer - problem

[lnaslavsky@xxxxxxxxxxx (Leila Naslavsky)]

Hi Marcos,
I'll keep looking, maybe the problem is elsewhere. Meanwhile, I'm adding 
the 'traceability' part i need by hand... 

Do you know if there was any changes in the ATL.ecore it self?

> Did you try to use AM3 and AMW with 3.1.0?

Yes, I tried to use both of them with 3.1.0. AMW worked, while when I 
tried to inject the atl file into a model with AM3 it always generates an 
empty model.

Maybe you could tell me which versions of ATL, AMW and AM3 I should be 
using, with which eclipse. (I've tried almost all the combinations :-)). I 
also tried checking out the source from cvs and generating the plugins my 
self.


Thanks,
Leila

> Regards,

> Marcos.

> Leila wrote:
> > Hi,
> > It looks like my last message was not posted. So here it goes again....
> > I'm trying to use the first transformation on ATL2WTracer, and I'm 
> > getting the following error:
> >
> > ****** BEGIN Stack Trace
> >     message: cannot set feature ATL!Module.elements to value 
> > org.eclipse.emf.ecore.impl.EObjectImpl@7848c5 (eClass: 
> > org.eclipse.emf.ecore.impl.EClassImpl@53673e (name: OclModel) 
> > (instanceClassName: null) (abstract: false, interface: false))
> >
> > It looks like the problem is that the code tries to add elements of type 
> > OclModel to the 'elements' attribute on ATL!Module. This makes sense 
> > since 'elements' is a list of type 'ModuleElement', not OclModel.
> >
> > What is odd it that in the former version of eclipse and emf (3.1.0, 
> > 2.1.0) that I was using, this transformation worked fine and I didn't 
> > get errors. Now I moved to 3.1.1, 2.1.1 (to be able to use AM3 and AMW), 
> > and I'm getting the errors.
> >
> > Do you have an idea of the reason? should I be changing the code to 
> > address that type issue?
> >
> > Thanks!
> >
> > Leila
> > Hi Marcos,