If your page class extends BasePage, I'm pretty sure you must have a
template. Have you tried putting an empty .html file next to the .page
spec?
On Thu, 11 May 2006 01:18:55 +0300, Rob Dennett <[EMAIL PROTECTED]>
wrote:
By the way, in the message below, the page I refer to has a
specification and a java class, but no template. That shouldn't matter,
should it?
Incidentally, I added <page name="MyPage"
specification-path="myDir/MyPage.page" /> to my application
specification and I still get the problem.
Thanks for your help,
Rob
-----Original Message-----
From: Rob Dennett
Sent: Wednesday, May 10, 2006 2:21 PM
To: users@tapestry.apache.org
Subject: page specifications in sub directories
I have a page specification in a sub directory of WEB-INF that doesn’t
seem to work.
If I enter
"http://localhost:8080/MyApp/app?service=external&page=myDir/MyPage”, I
get a PageNotFoundException saying that “myDir/MyPage” isn’t found. I
have read in much older threads that you needed to have a <page> tag in
the application specification for each page in a sub directory and
another thread saying that the above was the way to do it. The former
seems very inefficient (yeah, I know about the collectpages ant task).
Is it the only way to have page/component specs or templates in sub
directories?
BTW, what’s going on with apache.org? I haven’t been able to connect
for hours.
Thanks for your help,
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
