On 6/25/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
ok, I see. Thanks Ben for this important information.
But what happens, for example if I have the following structure:
2) pages.login.admin.AdminLogin
There's an outstanding bug for this, a case I didn't consider. It need
sto do somethin
ok, I see. Thanks Ben for this important information.
But what happens, for example if I have the following structure:
2) pages.login.admin.AdminLogin
2) pages.login.UserLogin
I have not tried but I guess the second one becomes: login/User, which is
reasonable. But what about the first: "login/?
User will now have the name "edit/User"
rather than "edit/EditUser". This results in shorter, clearer, more
natural URLs
cheers,
Ben
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 21 June 2007 4:59 PM
> To: users@
I noticed same strange behaviour in the site/class mapping of the
ComponentClassResolver. If the Classname contains text wich is identical to
directories where the class is in than the text is not contained in the key of
the map entry.
For example:
/mysite/admin/AdminLogin becomes /mysite/admin
