Just move the annotation out of the pages package. Although I don't know the internals of tapestry that well but I think because pages and components packages have live reloading they may be loaded from different classloaders...
regards Taha On Fri, Oct 22, 2010 at 7:19 PM, shinlang <sascha.hinl...@gameforge.de>wrote: > > Hi Thiago, > > thanks for your reply. I will certainly give that a try, but i won't be in > the office until monday. I'm not sure, if i stated my problem right (as i'm > quite new to tapestry). I am not dynamically adding the annotation to the > class, as far as i can see, so getting it from the component source should > work, shouldn't it? > > There is a test project that desscribes the problem, it can be found at > http://satansoft.de/tapestry/annotationtest.zip. > > In the TestFilter class you can see how i try to get the annotation from > the > page. > > Btw, i'm using Tapestry 5.2... > > Regards, > Sascha > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Annotations-and-ComponentRequestFilter-Problem-tp3232159p3232277.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
