Can you still do so, supporting the old packaged but deprecating
those annotations with the old packaging?
I think that now would be the time, since you're ramping up to release.
Christian.
On 13-Mar-08, at 19:11 , Howard Lewis Ship wrote:
I think it is safe to say that all annotations in
I think it is safe to say that all annotations in
org.apache.tapestry.annotations apply ONLY to Tapestry component
classes (components, mixins, pages, base).
Oops, that's not quite true; theres just a couple mixed in there that
are modifiers for @Inject and can work with IoC dependency injection.
Only classes controlled by tapestry.
That is, components, mixins, pages and base-classes
I hope I didn't miss any.
2008/3/13, Marcus <[EMAIL PROTECTED]>:
> Hi,
>
> @Property works for any class? or only for components and pages?
>
> thanks,
>
>
> Marcus
>
>
> On 3/13/08, Robert Zeigler <[EMAIL
Hi,
@Property works for any class? or only for components and pages?
thanks,
Marcus
On 3/13/08, Robert Zeigler <[EMAIL PROTECTED]> wrote:
>
> On Mar 13, 2008, at 3/139:07 AM , Angelo Chen wrote:
>
> >
> > Hi,
> >
> > As usual I always like to look at new features of every release,
> > here are
On Mar 13, 2008, at 3/139:07 AM , Angelo Chen wrote:
Hi,
As usual I always like to look at new features of every release,
here are
the one officially listed as new to the 5.0.11:
1. The @Cached annotation has been added to allowing the caching of
method
results.
Can't understand this,
Hi,
As usual I always like to look at new features of every release, here are
the one officially listed as new to the 5.0.11:
1. The @Cached annotation has been added to allowing the caching of method
results.
Can't understand this, any use case to explain this?
2. Tapestry can now generate ac
