I'm afraid I don't understand your example:
com.mydomain.myapp.pages.package1.Package1
then visit -
www.mydomain.com/myapp/package1
Of course this won't work, since 'package1' is not a page name. However
'package1/package1' should.
As for your trailing slash issue, I've not seen that one and it
certainly should never occur. Do your tests again just to be sure, and
if you still get them then there may need to be a bug report. If this is
happening its likely a server issue (im using jetty and have never seen
that).
chris
patrick whalen wrote:
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.
