Strangely, this only works if there's another class in the same package, and
you visit that page first. If you don't visit that page first, you get a 404
error. If you do, it works. After that, you can delete that other class and
it will continue to work, even if you restart the application.
To summarize:
create -
com.mydomain.myapp.pages.package1.Package1
then visit -
www.mydomain.com/myapp/package1
returns a 404 error, unless you create -
com.mydomain.myapp.pages.package1.TemporaryClass
then visit -
www.mydomain.com/myapp/package1/temporaryclass
you will then be able to visit -
www.mydomain.com/myapp/package1
without getting a 404 error.
patrick whalen wrote:
>
> I see now that it does work to put a class of the same name as the
> package, inside the package. The redundant name is then filtered out.
>
>
--
View this message in context:
http://www.nabble.com/-T5--Page-with-same-name-as-package-tf4497463.html#a12831853
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
