I think i might have found an interesting behavior in component
resolution. It seems that if you have a directory with the same name as
the page itself, Tapestry won't find that page.
So, it won't find pagetwo/PageTwo but it will find somepages/PageTwo.
At least this is the behavior i'm
This does solve my problem. So I'm moving forward...
Thanks.
-Steev Coco.
On Wed June 6 2007 5:17:55 am Hugo Palma wrote:
I think i might have found an interesting behavior in component
resolution. It seems that if you have a directory with the same name as
the page itself, Tapestry won't
Please add an issue to JIRA. I think what's happening is that
pagetwo/PageTwo.class is being aliased to the logical name pagetwo/
which is useless ... the code that does the mapping needs to be
careful not to alias down to nothing!
On 6/6/07, Hugo Palma [EMAIL PROTECTED] wrote:
I think i might
I have already
https://issues.apache.org/jira/browse/TAPESTRY-1541
Howard Lewis Ship wrote:
Please add an issue to JIRA. I think what's happening is that
pagetwo/PageTwo.class is being aliased to the logical name pagetwo/
which is useless ... the code that does the mapping needs to be
careful
On Wed June 6 2007 11:56:28 am Howard Lewis Ship wrote:
Please add an issue to JIRA. I think what's happening is that
pagetwo/PageTwo.class is being aliased to the logical name pagetwo/
which is useless ... the code that does the mapping needs to be
careful not to alias down to nothing!
I
: Wednesday, June 06, 2007 3:02 PM
To: Tapestry users
Subject: Re: (T 5.0.5 snapshot) No root element has been defined
Yes .. the idea is to strip out redundant junk in the URL (i.e., the
class name recapitulating the package name). The bug is that it goes
too far!
On 6/6/07, Daniel Jue [EMAIL
