If the annotations were @Contribute("...ApplicationDefaults") and
@Contribute("...ApplicationFilters") then the methods will work as expected
(without the annotations). Instead of looking for configuration from the
annotations, tapestry now determines that same configuration from the actual
wording of the method name. That is,
void contributeApplicationDefaults()
would do the same thing now as
@Contribute("...ApplicationDefaults")
void contributeFoo()
Hope this helps =]
On 3/21/07, Bogdan Calmac <[EMAIL PROTECTED]> wrote:
So after removing the annotations what should we do with the two
methods that were annotated: contributeApplicationDefaults() and
contributeApplicationFilters? I would guess nobody will call them
without the annotations.
Thanks,
Bogdan Calmac
On 3/20/07, Robert Zeigler <[EMAIL PROTECTED]> wrote:
> Because the tutorial is currently out of date with respect to the
> code-base.
> tapestry-ioc switched to flat namespacing which resulted in not
> needing Contribute or Id.
>
> Robert
>
> On Mar 20, 2007, at 3/202:54 PM , acarrara wrote:
>
> > Hello.
> >
> > On AppModule class of hilo application (Tapestry 5 tutorial) there
> > are some
> > imports:
> >
> > import org.apache.tapestry.ioc.annotations.Contribute;
> > import org.apache.tapestry.ioc.annotations.Id;
> >
> > but these classes (Contribute and Id) aren't on the
> > tapestry-ioc-5.0.3.jarpackage...
> >
> > Where are them?
> >
> > Thanks
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Peter Beshai
Computer Science Student
University of Waterloo
