You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Eric Everman <ev...@precedadesign.com> on 2003/04/18 20:00:23 UTC
Page Specification-Path Errors
Hi-
I am having problems specifying pages in the .application file - Tapestry
(alpha 5) doesn't seem to interpret them as on the classpath. For example,
this spec:
<page name="Home"
specification-path="/com/preceda/webnews/pages/ArticleEdit.page"/>
Results in this error:
Resource at context:/com/preceda/webnews/pages/ArticleEdit.page does not
exist.
While this spec:
<page name="Home"
specification-path="com/preceda/webnews/pages/ArticleEdit.page"/>
Results in this error:
Resource at context:/WEB-INF/com/preceda/webnews/pages/ArticleEdit.page
does not exist.
Based on the error messages, I found that this spec *did* work:
<page name="Home"
specification-path="classes/com/preceda/webnews/pages/ArticleEdit.page"/>
This is the first I've really played with the alpha 5 version - am I really
missing something here?
Thanks in advance,
Eric Everman
Preceda Design LLC
www.precedadesign.com
RE: Page Specification-Path Errors
Posted by Eric Everman <ev...@precedadesign.com>.
Thanks for that clarification. I placed my .application file at the
classpath root and set the org.apache.tapestry.application-specification
parameter and everything is working as expected.
Thanks for the help,
Eric Everman
At 4/18/2003, you wrote:
>Paths in the app spec are relative to the app spec. If the app spec is in
>the context (i.e., WEB-INF), then all paths must be there as well.
>Libraries are the exception, they are always on the classpath.
>
>If you want to mix and match, move the app spec onto the classpath.
>
>Search order for page specs:
>1) As defined in app spec
>2) In same folder as app spec.
>3) In WEB-INF/foo ("foo" is the name of the application servlet)
>4) In WEB-INF
>5) In application root (basically, "/" of WAR)
>
>--
>Howard M. Lewis Ship
>Creator, Tapestry: Java Web Components
>http://jakarta.apache.org/tapestry
>
>
>
> > -----Original Message-----
> > From: Eric Everman [mailto:everman@precedadesign.com]
> > Sent: Friday, April 18, 2003 2:00 PM
> > To: Tapestry users
> > Subject: Page Specification-Path Errors
> >
> >
> > Hi-
> >
> > I am having problems specifying pages in the .application
> > file - Tapestry
> > (alpha 5) doesn't seem to interpret them as on the classpath.
> > For example,
> > this spec:
> >
> > <page name="Home"
> > specification-path="/com/preceda/webnews/pages/ArticleEdit.page"/>
> > Results in this error:
> > Resource at
> > context:/com/preceda/webnews/pages/ArticleEdit.page does not
> > exist.
> >
> >
> >
> > While this spec:
> >
> > <page name="Home"
> > specification-path="com/preceda/webnews/pages/ArticleEdit.page"/>
> > Results in this error:
> > Resource at
> > context:/WEB-INF/com/preceda/webnews/pages/ArticleEdit.page
> > does not exist.
> >
> >
> >
> > Based on the error messages, I found that this spec *did* work:
> >
> > <page name="Home"
> > specification-path="classes/com/preceda/webnews/pages/ArticleE
> > dit.page"/>
> >
> >
> >
> > This is the first I've really played with the alpha 5 version
> > - am I really
> > missing something here?
> >
> > Thanks in advance,
> >
> > Eric Everman
> >
> > Preceda Design LLC
> > www.precedadesign.com
> >
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Page Specification-Path Errors
Posted by Luis Neves <ln...@netcabo.pt>.
Hi,
This is just a "me too" kind of message.
I also found this error recently, and was quite puzzled by it, even more so
because the *exact* same pages worked on Resin, but don't work on Jetty, so I
guess this is somekind of "environment" related issue ... sorry for not being
helpfull.
Best regards,
Luis Neves
On Friday 18 April 2003 19:00, Eric Everman wrote:
> Hi-
>
> I am having problems specifying pages in the .application file - Tapestry
> (alpha 5) doesn't seem to interpret them as on the classpath. For example,
> this spec:
>
> <page name="Home"
> specification-path="/com/preceda/webnews/pages/ArticleEdit.page"/>
> Results in this error:
> Resource at context:/com/preceda/webnews/pages/ArticleEdit.page does not
> exist.
>
>
>
> While this spec:
>
> <page name="Home"
> specification-path="com/preceda/webnews/pages/ArticleEdit.page"/>
> Results in this error:
> Resource at context:/WEB-INF/com/preceda/webnews/pages/ArticleEdit.page
> does not exist.
>
>
>
> Based on the error messages, I found that this spec *did* work:
>
> <page name="Home"
> specification-path="classes/com/preceda/webnews/pages/ArticleEdit.page"/>
>
>
>
> This is the first I've really played with the alpha 5 version - am I really
> missing something here?
>
> Thanks in advance,
>
> Eric Everman
>
> Preceda Design LLC
> www.precedadesign.com
Re: Page Specification-Path Errors
Posted by Jeevan Bihari <je...@yahoo.com>.
Eric,
I'm using Tapestry 2.4-alpha-5 and the following works for me:
<page name="Home" specification-path="/com/ABC/123/pages/Home.page"/>
I guess that's the first option you listed in your e-mail below. Maybe its an environment setup
problem ?
Jeevan
--- Eric Everman <ev...@precedadesign.com> wrote:
> Hi-
>
> I am having problems specifying pages in the .application file - Tapestry
> (alpha 5) doesn't seem to interpret them as on the classpath. For example,
> this spec:
>
> <page name="Home"
> specification-path="/com/preceda/webnews/pages/ArticleEdit.page"/>
> Results in this error:
> Resource at context:/com/preceda/webnews/pages/ArticleEdit.page does not
> exist.
>
>
>
> While this spec:
>
> <page name="Home"
> specification-path="com/preceda/webnews/pages/ArticleEdit.page"/>
> Results in this error:
> Resource at context:/WEB-INF/com/preceda/webnews/pages/ArticleEdit.page
> does not exist.
>
>
>
> Based on the error messages, I found that this spec *did* work:
>
> <page name="Home"
> specification-path="classes/com/preceda/webnews/pages/ArticleEdit.page"/>
>
>
>
> This is the first I've really played with the alpha 5 version - am I really
> missing something here?
>
> Thanks in advance,
>
> Eric Everman
>
> Preceda Design LLC
> www.precedadesign.com
>
__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com
RE: Page Specification-Path Errors
Posted by "Howard M. Lewis Ship" <hl...@attbi.com>.
Paths in the app spec are relative to the app spec. If the app spec is in
the context (i.e., WEB-INF), then all paths must be there as well.
Libraries are the exception, they are always on the classpath.
If you want to mix and match, move the app spec onto the classpath.
Search order for page specs:
1) As defined in app spec
2) In same folder as app spec.
3) In WEB-INF/foo ("foo" is the name of the application servlet)
4) In WEB-INF
5) In application root (basically, "/" of WAR)
--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/tapestry
> -----Original Message-----
> From: Eric Everman [mailto:everman@precedadesign.com]
> Sent: Friday, April 18, 2003 2:00 PM
> To: Tapestry users
> Subject: Page Specification-Path Errors
>
>
> Hi-
>
> I am having problems specifying pages in the .application
> file - Tapestry
> (alpha 5) doesn't seem to interpret them as on the classpath.
> For example,
> this spec:
>
> <page name="Home"
> specification-path="/com/preceda/webnews/pages/ArticleEdit.page"/>
> Results in this error:
> Resource at
> context:/com/preceda/webnews/pages/ArticleEdit.page does not
> exist.
>
>
>
> While this spec:
>
> <page name="Home"
> specification-path="com/preceda/webnews/pages/ArticleEdit.page"/>
> Results in this error:
> Resource at
> context:/WEB-INF/com/preceda/webnews/pages/ArticleEdit.page
> does not exist.
>
>
>
> Based on the error messages, I found that this spec *did* work:
>
> <page name="Home"
> specification-path="classes/com/preceda/webnews/pages/ArticleE
> dit.page"/>
>
>
>
> This is the first I've really played with the alpha 5 version
> - am I really
> missing something here?
>
> Thanks in advance,
>
> Eric Everman
>
> Preceda Design LLC
> www.precedadesign.com
>