Sounds like a good idea to me....

btw I was looking to figure out where I started going wrong in my
understanding. I fell victim to a  "confirmation bias" that was "confirmed"
by this page: http://tapestry.apache.org/tapestry5.1/tutorial1/first.html ,
which indicated that T5 required all templates be in the webapp directory.

It was also "confirmed" by the archetype tutorial1. I would suggest changing
the example to reflect the thinking of putting templates under resources or
in the java directories in a maven project.

thx

On Sun, Aug 8, 2010 at 1:42 PM, Howard Lewis Ship <hls...@gmail.com> wrote:

> The only exception is page templates which are allowed to be stored in the
> context root.  And in fact, if I were starting T5 again, that would not be
> supported. It may even be removed in a future release.
>
> On Sun, Aug 8, 2010 at 12:07 PM, Thiago H. de Paula Figueiredo <
> thiag...@gmail.com> wrote:
>
> > On Sat, 07 Aug 2010 20:34:29 -0300, Patrick Moore <patmo...@amplafi.com>
> > wrote:
> >
> >  Hi there --
> >>
> >
> > Hi!
> >
> >
> >  I am working to move our project from T4 to T5. In T4 we are using the
> >> tacos component resolver that allows the templates and properties files
> to
> >> be in the same directory.  In T5 how can we do the same thing?
> >>
> >
> > In Tapestry 5, it's mandatory you to put them in the same package.
> >
> >
> > --
> > Thiago H. de Paula Figueiredo
> > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
> > and instructor
> > Owner, Ars Machina Tecnologia da Informação Ltda.
> > http://www.arsmachina.com.br
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn
> how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>

Reply via email to