Directory Listings

2013-08-28 Thread alessio
Hi, I am using Wicket 1.5.3 in a WebSphere context and encountered an interesting behaviour which I dont fully understand. My application uses a /* mapping to WicketServlet and the application generally works fine. However I wonder what happens to static content (images, ) which is requested

Re: Directory Listings

2013-08-28 Thread alessio
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 or

Re: Directory Listings

2013-08-29 Thread alessio
directoryBrowsingEnabled setting. On Wed, Aug 28, 2013 at 7:23 PM, Sven Meier s...@meiers.net wrote: Wicket expects the path to end in a wildcard. Note that using WicketFilter instead of WicketServlet is recommended. Sven On 08/28/2013 05:07 PM, alessio wrote: Thanks, so basically the /* mapping should

Re: Directory Listings

2013-08-29 Thread alessio
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