Sorry, I might have been a bit too fast in posting, will dig some more and get back with better exceptions ...
/peter GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - New Energy for Data - The Graph Database. http://www.ops4j.org - New Energy for OSS Communities - Open Participation Software. http://www.qi4j.org - New Energy for Java - Domain Driven Development. On Fri, Feb 27, 2009 at 9:27 AM, Niclas Hedhman <[email protected]> wrote: > Maybe it is just me, but I can't follow what you have done, and what > the result is in the sample. Are you sure that it is CGLib issues you > are witnessing and not Dynamic Proxy issues? Is there any Exception > involved? > > Cheers > Niclas > > On Fri, Feb 27, 2009 at 4:20 PM, Peter Neubauer > <[email protected]> wrote: >> Hi, >> I am trying to get a basic Qi4j example working on Android. There is >> no support for bytecode enhancement a la cglib, so I commented that >> out, which means I cannot use Abstract Mixins atm. For the compiste >> side of things, that is no big deal, you can still do >> @Mixins( { HelloWorldMixin.class, CompositeMixin.class, >> HelloWorldStateMixin.class } ) >> public interface HelloWorldComposite >> extends HelloWorld, Composite >> { >> } >> >> with CompositeMixin taking over the generic functionality and the >> HelloWorldStateMixin being declared explicitly on the composite. >> >> However, the usage of Propertydoes seem to involve abstrace handling. >> My HelloWorldStateMixin looks like >> public class HelloWorldStateMixin implements HelloWorldState { >> private Property<String> name; >> >> �...@override >> public Property<String> name() { >> // TODO Auto-generated method stub >> return name; >> } >> >> �...@override >> public Property<String> phrase() { >> // TODO Auto-generated method stub >> return phrase(); >> } >> } >> >> and >> >> public class HelloWorldMixin >> implements HelloWorld >> { >> �...@this HelloWorldState state; >> >> public String say() >> { >> return state.phrase().get() + " " + state.name().get(); >> //return "Hello World"; >> } >> } >> >> results still in abstract classes being used dynamically when using . >> Is there any single point of interest to change Property handling for >> this? >> >> >> Doing >> public interface HelloWorldState >> { >> String phrase(); >> String name(); >> } >> >> , the according HelloWorldStateMixin and >> public class HelloWorldMixin >> implements HelloWorld >> { >> �...@this HelloWorldState state; >> >> public String say() >> { >> return state.phrase() + " " + state.name(); >> } >> } >> >> works fine, it seems to be the Property handling that is the problem ... >> >> /peter >> >> GTalk: neubauer.peter >> Skype peter.neubauer >> Phone +46 704 106975 >> LinkedIn http://www.linkedin.com/in/neubauer >> Twitter http://twitter.com/peterneubauer >> >> http://www.neo4j.org - New Energy for Data - The Graph Database. >> http://www.ops4j.org - New Energy for OSS Communities - Open >> Participation Software. >> http://www.qi4j.org - New Energy for Java - Domain Driven Development. >> >> _______________________________________________ >> qi4j-dev mailing list >> [email protected] >> http://lists.ops4j.org/mailman/listinfo/qi4j-dev >> > > > > -- > http://www.qi4j.org - New Energy for Java > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > > _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
