Jeremy Levy wrote:
On Fri, May 2, 2008 at 9:37 AM, Scott Sauyet <[EMAIL PROTECTED]> wrote:
I'm having a problem with different behavior when my Wicket application
runs on Jetty versus on Tomcat, and I'm wondering if anyone has a suggestion
as to why. [ ... ]
It sounds like this:
https://issues.apache.org/jira/browse/WICKET-1205
That was exactly it. Thank you.
Unfortunately, this issue has not been resolved as of Wicket 1.3.3.
There was a bizarre note at the end of that issue from Al Maw that it
had something to do with having an "index.jsp" page in the application.
Sure enough, when I removed that page, it seems to work fine.
The client wanted that "index.jsp" for consistency with the application
that I'm replacing. I will find out exactly how important that is. I'd
really rather not go with the "app/*" route unless necessary. But I'm
curious if anyone has figured out a solution to the underlying problem.
Thanks again, Jeremy.
Al,
I'm CC'ing you because in the last notes I saw for issue 1205 you were
off to try to fix this. Did you ever get a useful test project to
duplicate the error? If not, I can try to create something, although
I'm not much of a Maven user. Just let me know.
-- Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
