On 2/7/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
I just checked in a fix for your problem.
The new behavior is as I described, the "/Foo.html" is really the html
event triggered on the root component of page Foo. You will likely not
have any onHTML() event handler methods, and the defaul
I just checked in a fix for your problem.
The new behavior is as I described, the "/Foo.html" is really the html
event triggered on the root component of page Foo. You will likely not
have any onHTML() event handler methods, and the default behavior will
be to redirect back to page foo (i.e., "/f
Earlier versions of Tapestry 5 did use ".html" as the extension that
identifies a page render (rather than an event trigger on a
component).
Howerver, I'll look into your case. This should have triggered an
"html" event (which is meaningless) on the Home page itself, and that
should have resulted
You have the wrong URL. It's
http://localhost:8080/tapestry_empty/Home
not
http://localhost:8080/tapestry_empty/Home.html
page urls don't have the file extension.
Stranzenbach, Ralf wrote:
It's an access to
http://localhost:8080/tapestry_empty/Home.html
Mit freundlichen Grüßen,
