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 hivemodule.xml.
On 11/14/07, Andreas Andreou <[EMAIL PROTECTED]> wrote: > Also, > http://wiki.apache.org/tapestry/PagesAndComponentsInWEB-INF > http://wiki.apache.org/tapestry/SpeclessPagesInWEB-INF -- What you want today, may not exist tommorrow Blog: http://joshuajava.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]