OK, so since I'm having this problem and no one else is -- what am I
doing wrong?
And why is it working in Firefox? In Firefox, with javascript disabled,
I get a normal POST; with javascript enabled, I get ajax.
In IE 8, using Wicket 1.4.9, even with javascript enabled, I get a POST
(the "fallback" part of the AjaxFallbackButton), but with Wicket 1.4.17,
I have broken ajax (because of the transport), but I also don't get a
fallback POST.
I'm thrilled if the fault lies with me, because that's presumably easier
to fix. But what am I (not) doing that breaks this?
On 7/29/2011 6:11 AM, Martin Grigorov wrote:
1.4.17 is in use by many people and you're the only one having this problem.
1.5.x and 1.4.x are the same related to WICKET-3887.
AjaxLink/AjaxFallbackLink cannot do POST request unless you override
parts of them.
On Fri, Jul 29, 2011 at 7:54 AM, T P D<li...@diffenbach.org> wrote:
Wicket 1.4.9's Ajax doesn't work in Internet Explorer; in particular,
AjaxFallbackButtons fall back to non-Ajax POSTs, and the Wicket Debug
"window" is never seen.
In 1.4.17, Ajax is still broken, but the fallback never happens, because
Ajax sort-of works: the the Wicket Debug "window" doe show up, and when the
AjaxFallbackButton is clicked, a attempt is made to to XMLHTTP, but fails
with "Automation server can't create object".
This looks like the same bug as reported in
https://issues.apache.org/jira/browse/WICKET-3887 and
https://issues.apache.org/jira/browse/WICKET-1432. It's apparently fixed in
1.5, but while bug 3887 is claimed to be fixed in 1.4.18, the latest
snapshot exhibits the same behavior as 1.4.17.
---------------------------------------------------------------------
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
