[
https://issues.apache.org/jira/browse/WICKET-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg updated WICKET-3427:
----------------------------------
Description:
sometimes these errors pop-up:
ERROR - RequestCycle - Error during processing error message
java.lang.IllegalStateException: Current ajax request is missing the base url
header or parameter
at org.apache.wicket.util.lang.Checks.notNull(Checks.java:37)
and when this happens, the ajax debug window shows
ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not find
root <ajax-response> element
ERROR: Wicket.Ajax.Call.failure: Error while parsing response: console is not
defined
and when trying to hit another ajax element, this shows up:
INFO: Channel busy - postponing...
I'll be attaching a quickstart -- however I cannot reproduce the problem via
the wickettester. It just happens when clicking around in the browser.
Sometimes it just works, but more often the error shows up after clicking links
only 2 times.
It seems to be related to having ajax components INSIDE the components which
are triggered through the event mechanism.
was:
sometimes these errors pop-up:
ERROR - RequestCycle - Error during processing error message
java.lang.IllegalStateException: Current ajax request is missing the base url
header or parameter
at org.apache.wicket.util.lang.Checks.notNull(Checks.java:37)
and when this happens, the ajax debug window shows
ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not find
root <ajax-response> element
ERROR: Wicket.Ajax.Call.failure: Error while parsing response: console is not
defined
and when trying to hit another ajax element, this shows up:
INFO: Channel busy - postponing...
I'll be attaching a quickstart -- however I cannot reproduce the problem via
the wickettester. It just happens when clicking around in the browser.
Sometimes it just works, but more often the error shows up after clicking links
only 2 times.
It seems to be related to having ajax components INSIDE the components which
are triggered through the event mechanism.
Summary: Error in wicket-ajax.js when trying to log debug messages to
js console (was: new event mechanism + ajax giving ajax request errors)
> Error in wicket-ajax.js when trying to log debug messages to js console
> -----------------------------------------------------------------------
>
> Key: WICKET-3427
> URL: https://issues.apache.org/jira/browse/WICKET-3427
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.5-RC1
> Environment: ubuntu 10.04.1 amd64
> Reporter: Antoine van Wel
> Assignee: Igor Vaynberg
> Fix For: 1.5-RC2
>
> Attachments: eventsandajax.tar.gz
>
>
> sometimes these errors pop-up:
> ERROR - RequestCycle - Error during processing error message
> java.lang.IllegalStateException: Current ajax request is missing the base url
> header or parameter
> at org.apache.wicket.util.lang.Checks.notNull(Checks.java:37)
> and when this happens, the ajax debug window shows
> ERROR: Wicket.Ajax.Call.failure: Error while parsing response: Could not find
> root <ajax-response> element
> ERROR: Wicket.Ajax.Call.failure: Error while parsing response: console is not
> defined
> and when trying to hit another ajax element, this shows up:
> INFO: Channel busy - postponing...
> I'll be attaching a quickstart -- however I cannot reproduce the problem via
> the wickettester. It just happens when clicking around in the browser.
> Sometimes it just works, but more often the error shows up after clicking
> links only 2 times.
> It seems to be related to having ajax components INSIDE the components which
> are triggered through the event mechanism.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
