I kinda get the idea now that Tapestry by default looks for page &
component specification under WEB-INF. But what I don't get is why do
we have to create a class that implements
ISpecificationResolverDelegate and then configure it again in
hivemodule.xml instead of just configuring it in hivemodul
Also,
http://wiki.apache.org/tapestry/PagesAndComponentsInWEB-INF
http://wiki.apache.org/tapestry/SpeclessPagesInWEB-INF
On Nov 14, 2007 4:09 PM, Jim <[EMAIL PROTECTED]> wrote:
> Hi Joshua,
>
> If you look through the configuration guide:
> http://tapestry.apache.org/tapestry4/UsersGuide/configura
Hi Joshua,
If you look through the configuration guide:
http://tapestry.apache.org/tapestry4/UsersGuide/configuration.html,
under "Application extensions", you'll find the following two entries in
the table:
org.apache.tapestry.specification-resolver-delegate
ISpecificationResolverDelegate
A
Hi Jim,
Thanks for replying. But isn't it possible to configure this just
using hivemodule.xml without having to create the classes you've
mentioned? Since I'm still new to this and do not have any idea how
would the class look like.
Thanks
On 11/13/07, Jim <[EMAIL PROTECTED]> wrote:
> Tapestry'
Joshua Jackson wrote:
Dear all,
By default T4 files such as *.jwc, *.page, *.html are required to be
place inside WEB-INF/.
But I find this quite messy when there are other configuration from
another framework. Is there any way I can move these files to another
folder?
Thanks in advance
H
