Does nobody else want to comment? If there are no objections I'll go ahead and remove any start-page support from ComponentClassResolverImpl and will make start-pages unusable below anything but /.
Uli On 10.02.2011 14:11, Ulrich Stärk wrote: > On 10.02.2011 13:19, Howard Lewis Ship wrote: >> 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 >> > > That means that pages.foo.StartFoo will never ever be available as > /pages/foo/ whereas pages.Start, > and only that one, will be available as /. Hopefully we won't break any > existing apps that way... > > Uli > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
