I don't know if it's the same problem, but in order to get wicket ajax
working in firefox, I patch line 836 in wicket-ajax.js (it's line 836
for wicket-1.3.4, may be a different line number for other versions) from
if (Wicket.Browser.isGecko()) {
to
if (Wicket.Browser.isGecko() && url.match("^http://";) == null) {
otherwise I also get 404 errors because it adds http://localhost:8080/
to the url which already contains it..
prasana wrote:
I am not sure whether I have to post the issue here or in Wicket mailing
list. So I am posting it in both the places.
I have a wicket portlet that runs on jetspeed portal which makes a Ajax
Request.
When I first add the portlet to the page, all the ajax requests are working
fine.
Once I visit some other pages in the portal and come back to the wicket
portlet, all the ajax requests are giving a response code of 404. The issue
is happening only in firefox.
The wicket ajax debugger shows the following message
ERROR: Received Ajax response with code: 404
Once I remove the portlet and add it again to the page, the ajax requests
are working fine. Also I am giving the the .psml file directly in the
address bar, the ajax requests are working fine. But when jetspeed creates
the URL with its own navigational state parameters, then all the ajax
requests stopped working.
On further digging in, I found out that in ContainerValve the following
condition is true and the 404 response is sent back to the browser for Ajax
Request.
if (window != null && page.getFragmentById(window.getId().toString()) ==
null)
{
// target window doesn't exists anymore or the target page is not
accessible (anymore)
request.getResponse().sendError(HttpServletResponse.SC_NOT_FOUND);
return;
}
Any help regarding on how to fix this is really appreciated.
Thanks
Prasanna
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
