should not interfere with
non-Wicket requests?
In other words, static content as well as potential directory listings
(respectively related error messages if disabled) will always be
passed on and served by the underlying application server (be it
WebSphere or Tomcat or .), correct
not interfere with
non-Wicket requests?
In other words, static content as well as potential directory listings
(respectively related error messages if disabled) will always be
passed on and served by the underlying application server (be it
WebSphere or Tomcat or .), correct?
Would you know why
of WicketServlet is recommended.
Sven
On 08/28/2013 05:07 PM, alessio wrote:
Thanks, so basically the /* mapping should not interfere with
non-Wicket requests?
In other words, static content as well as potential directory listings
(respectively related error messages if disabled) will always
On Thu, Aug 29, 2013 at 10:59 AM, Sven Meier s...@meiers.net wrote:
Sorry, that is what I meant. Read the source Luke! ;).
I dont believe I understand your hint :)
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
a clue what is going on here and whether Wicket
actually returns directory listings at all?
Thanks
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Wicket passes such requests back to the default handler
Yes, see WicketServlet#fallback()
whether Wicket actually returns directory listings at all?
No, it doesn't.
Regards
Sven
On 08/28/2013 03:40 PM, alessio wrote:
Hi,
I am using Wicket 1.5.3 in a WebSphere context and encountered
Thanks, so basically the /* mapping should not interfere with
non-Wicket requests?
In other words, static content as well as potential directory listings
(respectively related error messages if disabled) will always be
passed on and served by the underlying application server (be it
WebSphere
as potential directory listings
(respectively related error messages if disabled) will always be
passed on and served by the underlying application server (be it
WebSphere or Tomcat or .), correct?
Would you know why the StringIndexOutOfBoundsException occurs when I
map the servlet to / without
