|
|
|
Re: [Acceleo] Resource Factory issue [message #709724 is a reply to message #708779] |
Thu, 04 August 2011 08:23   |
|
Simon,
Your generated Java launcher should already have the required resource factory registered from its "registerResourceFactories" method if it did work with Acceleo 3.0.3. Otherwise, that could be a difference between the Eclipse in which you had 3.0.3 installed and the Eclipse in which you have 3.1.0 (was your "podml" metamodel plugin installed in that previous Eclipse? Is it in the new?). It could also be a difference in the order in which you do things : if you double-click a "podml" file in your workspace, is it properly loaded in its generated editor (if you generated the editor code)? Is it even recognized as an ecore model, or is it opened in the text editor when you double-click it? It it does open in its own editor and not in the text editor, you should not see the problem again if you re-launch the Acceleo generator.
In other words ... no, there is no difference in resource factory handling between Acceleo 3.0.3 and Acceleo 3.1.0 that I know of. However the resource factory *does* need to be registered somewhere. If it is not by your Acceleo launcher, it must be by one of the plugins : either the podml plugin if you install it in your Eclipse, or EMF itself when you will try to open a podml file in an editor.
Laurent Goubet
Obeo
|
|
|
Re: [Acceleo] Resource Factory issue [message #709927 is a reply to message #709724] |
Thu, 04 August 2011 13:39   |
simon.vivien Messages: 21 Registered: August 2011 |
Junior Member |
|
|
Hi,
My podml files DO open in their generated editor, so the metamodel plugin seems to be correctly installed.
However, I forgot to mention that my resource factory is handled by Xtext (2.0), and that it worked under Acceleo 3.0.3/Xtext 2.0. Maybe it is some compatibility problem between Acceleo 3.1 and Xtext 2.0
Regards,
Simon.
[Updated on: Thu, 04 August 2011 13:40] Report message to a moderator
|
|
|
|
Re: [Acceleo] Resource Factory issue [message #710589 is a reply to message #710059] |
Fri, 05 August 2011 07:36   |
|
Hi Ed, Simon,
This incompatibility is not something we were aware of, nor was the way to register the Xtext resource factory through a "doSetup".
Simon, If you try and use Acceleo 3.0.3 in the very same environment you are in now, are you sure that the generation indeed works successfuly? i.e : is it really _only_ Acceleo that changed or is this incompatibility really coming from a number of factors? When you use Ed's suggestion of registering the factory though the "standaloneSetup.doSetup()" method, is the problem fixed?
If it does, this is definitely something we have to document somewhere, since AFAIK working with Xtext models as input of Acceleo generations was really straightforward before.
Laurent Goubet
Obeo
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02233 seconds