I had a very similar problem and unfortunately called it a day. If memory serves it's the way iPOJO is scanning for references. You may have better luck using the @CompileStatic annotation on the class which may help.
On Mon, Jul 21, 2014 at 7:00 PM, Paulo Renato de Athaydes < [email protected]> wrote: > I have tried all I could... unfortunately IPojo does not seem to work > with Groovy classes.But that's ok, the Java Component can always hand over > the real work to some Groovy class. > > > Renato > > Date: Mon, 21 Jul 2014 11:57:04 +0200 > > From: [email protected] > > To: [email protected] > > Subject: Re: Using IPojo and Groovy > > > > Hi, > > > > On 20 juillet 2014 at 23:57:53, Paulo Renato de Athaydes ( > [email protected]) wrote: > > Hi. > > I wrote a little IPojo application and it works great, except when I try > to use Groovy in one of the bundles (to design the UI, which is a great job > for using Groovy). > > I noticed that the IPojo manipulator did not seem to know how to deal > with Groovy so no IPojo metadata was added to the manifest and I assume no > bytecode was altered as it should have. > > Is there any way to make a @Component written in Groovy work? > > The iPOJO manipulator handles bytecode, so as soon as you have the byte > code of a class annotated with @Component, it should be manipulated. Just > be sure that the .class are generated at compile time. > > > > Cheers, > > > > > > > > Clement > > > > > > Thanks, > > Renato > > -- Many thanks, Miles Burton
