However, you can use a fairly simple SpecificationResolverDelegate to have your 
HTML files under WEB-INF and have specless pages.  I don't have access to my 
dev machine right now or I'd post the details.  Searching through the archives 
of this list you should be able to find more information.  
 
This comes up often enough that I should probably put up a doc on the wiki 
describing how to do it.
 
jeff

________________________________

From: Geoff Longman [mailto:[EMAIL PROTECTED]
Sent: Mon 2/13/2006 5:54 PM
To: Tapestry users
Subject: Re: Newbie : Tapestry 4 Disgarding the Page Specification



> Can anyone explain or point to where in the Tapestry docs that it discusses 
> why
> you have to move your html files to web root if you don't use page
> specifications.

http://jakarta.apache.org/tapestry/UsersGuide/template.html#template.locations

"In addition, any HTML template in the web application context is
considered a page, even if there is no matching page specification."

>Also with your html files in the web root directory is there
> any strategies that are used in the tapestry community to prevent a user from
> calling an HTML file directly from the browser and not having it protected by
> being in the WEB-INF directory, or am I missing something and tapestry is
> protecting me from this problem...I am a struts user and just trying to get 
> into
> the tapestry way of thinking.

This is one of the downsides of specless pages for sure.

Geoff

>
> Thanks again everyone for the help....cheers.
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
The Spindle guy.          http://spindle.sf.net
Get help with Spindle:  
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Blog:                     http://jroller.com/page/glongman
Feature Updates:          http://spindle.sf.net/updates

---------------------------------------------------------------------
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]

Reply via email to