On Sun, 02 Feb 2014 17:05:28 -0200, Bob Harner wrote:
I'm with Lance in thinking that an exception should be thrown. The
exception message should list the conflicting page names, of course.
I prefer to have Tapestry check the longer URL before using the shorter
one, as in 99.9% of the time
I'm with Lance in thinking that an exception should be thrown. The
exception message should list the conflicting page names, of course.
On Jan 31, 2014 10:38 AM, "Mauricio Aldazosa"
wrote:
> On Thu, Jan 30, 2014 at 2:35 AM, Lance Java >wrote:
>
> > > but I'd also call that a very confusing namin
On Thu, Jan 30, 2014 at 2:35 AM, Lance Java wrote:
> > but I'd also call that a very confusing naming of pages.
>
>
Granted :-), we have already changed the names. I also created a jira
issue: https://issues.apache.org/jira/browse/TAP5-2281 for it. I'll be
happy to provide a patch if a consensus i
> but I'd also call that a very confusing naming of pages.
Agreed! I'd say a possible 'fix' would be for Tapestry to throw exception
when it encounters the two ambiguous pages at startup.
On Wed, 29 Jan 2014 15:50:51 -0200, Mauricio Aldazosa
wrote:
Hi guys,
Hi!
We recently got into a little bit of trouble with Tapestry's URL
shortening. We have a ComponentRequestFilter that restricts access to
pages based on annotations placed on the pages classes.
With the following s
Hi guys,
We recently got into a little bit of trouble with Tapestry's URL
shortening. We have a ComponentRequestFilter that restricts access to pages
based on annotations placed on the pages classes.
With the following setup, tapestry gets mixed up about the page annotations:
1. We have a pag
