| [Acceleo 3.0.1] Error notifying registry change listener. [message #643561] |
Tue, 07 December 2010 12:46  |
 Manuel Selva
Messages: 189
Registered: July 2009
Location: Grenoble, France |
Senior Member |
|
|
Hello there,
I am starting to play with Acceleo 3 in order to automate one repetitive tasks of my daily work as Eclipse plugin developer.
In this context I want to generate several Java classes from an EMF model (xmi file) conform to a given meta model (an ecore file). This is done manually by myself during development stage, no need to programatically generate code.
Using for loops and the file tag, I successfully generated my class files for all model elements. Now I need to generate the content of the file, and for this I need an other for loop inside the file tag. After added this loop I always get many errors (crashing my workbench) of type:
"Error notifying registry change listener."
Any ideas why ? How can I solve this blocking issue please ?
Any help would be really appreciated,
Thanks in advance
Manu
http://manuelselva.wordpress.com/
[Updated on: Tue, 07 December 2010 13:05] Report message to a moderator |
|
|
|
| Re: [Acceleo 3.0.1] Error notifying registry change listener. [message #643796 is a reply to message #643564] |
Wed, 08 December 2010 09:53  |
|
This is a multi-part message in MIME format.
--------------060001080200040309090403
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Manuel,
This is due to us relying on OSGi's "hot removing" of bundles, but some
plugins aren't being good citizens with their extension points : when we
(Acceleo) remove said plugins, their contributions to the plugin
registry remain... and you get the error you observed.
This is a known Acceleo limitation. As we can't expect the plugin
designers to change their extension points to accept hot
plugging/removing, we need to find a way to workaround this issue ...
but don't expect this workaround to be there before 3.1M6 at least.
For the time being, your options are limited : this issue comes from
Acceleo's dynamic mode. When you launch the generator located in plugin
A, we'll walk the workspace projects in order to check whether one of
them is a dependency of A. If A or one of its dependencies is in the
workspace, and extends an extension point that presents the issue of not
being dynamic, you'll have this error. You can then :
- remove from your workspace the dependencies you don't need to be there
(if they're already installed)
- launch a runtime Eclipse and launch your generation from there (either
with only your generator project in the workspace or, even better,
having defined an action to launch the generation from a right-click, a
menu...)
This will be investigated (and, hopefully, fixed) before 3.1 goes live,
but I can't give any more precise date.
Laurent Goubet
Obeo
On 07/12/2010 14:06, Manuel Selva wrote:
> After more investigations it seems it's not related to a for loop in a
> file tag. In fact the problem start occurring the second time i am
> launching my "Generate" Acceleo launch configuration.
>
> Manu
--------------060001080200040309090403
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"
YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------060001080200040309090403--
|
|
|
|
Powered by
FUDForum. Page generated in 0.03875 seconds
] 
Search
Help
Register
Login
Home
