The reason for the 404 is the Websphere is checking for a file, then intending to filter before and after serving up the file. Since it finds no file to serve, it returns the 404.
-Clint On Mon, May 2, 2011 at 9:33 AM, D D <dawi...@gmail.com> wrote: > FYI. I added the index.htm file to my project and everything now > works. This is very strange and if anyone has an insight why this > helped I would be very glad to read about it. > > Since I didn't try switching to servlet I'm not sure if that would > have helped as well. > > Thank you for all of your suggestions! > > Dave > > On Mon, May 2, 2011 at 6:18 AM, James Carman <ja...@carmanconsulting.com> > wrote: > > Try changing it to a servlet. There's another thread going on here > > just recently which gives an example. > > > > On Sun, May 1, 2011 at 10:22 PM, D D <dawi...@gmail.com> wrote: > >> I have a filter in web.xml file - however I did not set it up. At the > >> same time I've started to question the setup because I tried to deploy > >> a "clean" test app (by clean I mean new ear file for the test app and > >> no extra ear files and configuration - just a strip down example from > >> wicket's website) and I'm getting 404 trying to bring the application > >> up. > >> > >> So the original application with problem is having 404 on ajax calls > >> but it will start up. Test app will not start up - shows 404 all the > >> time. > >> > >> Is it a WAS setup issue? > >> > >> Thanks, > >> Dave > >> > >> > >> On Sun, May 1, 2011 at 8:57 PM, James Carman < > ja...@carmanconsulting.com> wrote: > >>> You are using a servlet instead of a filter, right? I don't see the > >>> entire conversation in my gmail, here, so I hope I didn't miss > >>> something. > >>> > >>> On Sun, May 1, 2011 at 9:51 PM, D D <dawi...@gmail.com> wrote: > >>>> I tried the setting with true and false settings. It still doesn't > work. > >>>> > >>>> Here is Ajax Debug > >>>> INFO: Initiating Ajax GET request on > >>>> > ?wicket:interface=:0:dataForm:dataPanel:rxEntryTabs:panel:link::IBehaviorListener:0:-1&random=0.6781234819490185 > >>>> INFO: Invoking pre-call handler(s)... > >>>> ERROR: Received Ajax response with code: 404 > >>>> INFO: Invoking post-call handler(s)... > >>>> INFO: Invoking failure handler(s)... > >>>> INFO: focus removed from link30 > >>>> > >>>> > >>>> I also traced through debug the response sent to HttpResponse object > >>>> and it's what I'm expecting: > >>>> > >>>> “<?xml version="1.0" encoding="UTF-8"?><ajax-response><component > >>>> id="counter31" ><![CDATA[<span id="counter31">5</span>]]></component> > >>>> </ajax-response>” > >>>> > >>>> Not only it's written but the response object is properly closed too. > >>>> Not a single exception is thrown in Wicket's code. > >>>> > >>>> The problem has to be somewhere inside WAS processing, right? > >>>> > >>>> Any ideas where? > >>>> > >>>> Dave > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >>>> For additional commands, e-mail: users-h...@wicket.apache.org > >>>> > >>>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >>> For additional commands, e-mail: users-h...@wicket.apache.org > >>> > >>> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
