Hi, Thanks for your answers. I tried with Taspestry 5.2.0 but I still get the problem. After some investigations it looks like that the unrecognized methods are not synthetic. Actually, every JavaFX object extends the com.sun.javafx.runtime.FXBase class bringing those unrecognized methods. So the problem is slightly different than for Groovy. I'll create a JIRA about this.
Cheers, Antoine On Wed, May 26, 2010 at 9:22 AM, Kristian Marinkovic < [email protected]> wrote: > hi, > > there was a issue that already has been fixed: > https://issues.apache.org/jira/browse/TAP5-839 > > g, > kris > > > > Von: "Thiago H. de Paula Figueiredo" <[email protected]> > An: "Tapestry users" <[email protected]> > Datum: 25.05.2010 15:06 > Betreff: Re: [Taspetry IoC] Using Tapestry IoC with JavaFX > > > > On Tue, 25 May 2010 08:50:45 -0300, Antoine Mischler <[email protected]> > wrote: > > > Hi guys, > > Hi! > > > followed by a bunch of unrecognized methods. I think these methods are > > automatically generated by the javafx compiler. > > So my question is: is there a way to make the registry less sensible to > > unrecognized methods? > > There was the same problem with writing module classes in Scala or Groovy, > > I don't remember exactly. This was already addressed in Tapestry-IoC with > some explicit checks. Post a JIRA about it so the committers can take a > look at it. Please include a sample project to speed up the process. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- Antoine Mischler www.dooapp.com +33 (0)6 50 90 72 94
