Yes, good idea. But I am still using java 1.4, and have no idea to enable annotation. Actually I think cachable methods should be a solid method rather than an abstract one.
Yunfeng Hou --- "Dmitry I. Zubarovsky" <[EMAIL PROTECTED]> wrote: > Hello Yunfeng! > > Do not you think its also make sense to annotate > getter methods,needs > to be cached, in component class. > like this: > > @Cached > public abstract void getFoo() > > Regards, > Dima > > YH> I add cached property support to tapestry. A > cached > YH> property is actually a method in the form of a > getter, > YH> which will return an object could be used by > page > YH> components for several times, and worth cache > it. For > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
