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

Reply via email to