On Thu, Feb 10, 2011 at 3:37 AM, Ulrich Stärk <[email protected]> wrote: > There is a bug in ComponentClassResolverImpl that gives a start page as > configured with > SymbolConstants.START_PAGE_NAME precedence over an existing Index page in > certain cases. If for > example the pages example.pages.exam.ExamIndex and > example.pages.exam.StartExam exist, the exam/ URL > will map to StartExam instead of to ExamIndex as one might expect. > > The question is: What is the desired behaviour in that case. > > Should Start pages other than at the root level be ignored alltogether? >
+1 > Should index pages in subpackages have precedence over Start pages? > +1 > Should Start pages in subpackages have precedence over Index pages? > The Start page logic should only, IMO, apply to the root path, i.e., "/". If a Start page exists, it should match "/" (with no page activation context). Otherwise, it should match the root Index page (with anything else on the path as page activation context). > Uli > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
