All I can say for this is ... the 5.1 code tracks whats going on, and reports it when an exception occur. Makes tracking this stuff down much easier. You're not making any contribution to Alias?
On Mon, Feb 9, 2009 at 3:59 PM, Thiago H. de Paula Figueiredo <thiag...@gmail.com> wrote: > One situation that can raise that exception is the existence of non-static > methods in Tapestry-IoC class modules (for example, AppModule). I've had > this problem once. By the way, it happened for more people in this list too, > so check the archives. ;) > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
