The WebRequestCyclyProcessor substitutes without warnings or error
messages ajax requests, when wicket is at the same time processing page
requests for that page. This may break applications that serve
non-shared resources such as images (which will also trigger erquests to
the page), and do ajax
Yeah it's a problem, Im having trouble with it too.. Im not sure what
can be done or if anyone are on it?
Pointbreak wrote:
As always, it doesn't work. I think every time I look at it (which is
quit often) it gives errors because of the vcs connection. I would like
it to build a new version of
i think it is sourceforge that thinks we are bombarding them or something
like that
if only we could make it clear that it is a build server and that that ip is
fine
johan
On Thu, Sep 18, 2008 at 10:32 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL PROTECTED] wrote:
Yeah it's a
Has anyone written them... Otherwise i'll do it..
Johan Compagner wrote:
i think it is sourceforge that thinks we are bombarding them or something
like that
if only we could make it clear that it is a build server and that that ip is
fine
johan
On Thu, Sep 18, 2008 at 10:32 AM, Nino
I did it here:
http://sourceforge.net/tracker/index.php?func=detailaid=2117575group_id=1atid=21
Johan Compagner wrote:
i think that is already done before but sending more emails to them cant
hurt at all
On Thu, Sep 18, 2008 at 10:51 AM, Nino Saturnino Martinez Vazquez Wael
[EMAIL
I have never seen any problems with the check.
The reason is that some browsers fire the ajax request even after user has
already clicked another link on page (normal page request). That can have
negative impact on the server side state. e.g.
user is on page 1 version 1
clicks an ajax link and
