[
https://issues.apache.org/jira/browse/WICKET-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185658#comment-13185658
]
Stefan Schueffler edited comment on WICKET-3596 at 1/13/12 4:38 PM:
--------------------------------------------------------------------
I just want to report the same behaviour in wicket 1.4.19
("Error: Wicket.functionExecuterCallbacks.script1 is not a function" on first
page-load, and on all subsequent page loads it works like a charm).
On first page load, wicket-event.js and wicket-ajax.js do have a
";jsessionid=..." parameter.
When the user now clicks on some ajax-enabled link, the ajax-request gets
triggered, and the xml-response from the server looks fine.
In the xml-response there now is a header-contribution for wicket-ajax.js and
wicket-event.js (without sessionid).
The browser now loads both script-files again (without sessionid, utilizing the
cookie instead), and then raising the javascript-exception mentioned earlier.
was (Author: schueffi):
I just want to report the same behaviour in wicket 1.4.19
("Error: Wicket.functionExecuterCallbacks.script1 is not a function" on first
page-load, and on all subsequent page loads it works like a charm).
> Problem with ajax requests in rc3 with browsers other than chrome
> -----------------------------------------------------------------
>
> Key: WICKET-3596
> URL: https://issues.apache.org/jira/browse/WICKET-3596
> Project: Wicket
> Issue Type: Bug
> Reporter: Martin Cassidy
> Assignee: Martin Grigorov
> Fix For: 1.5-RC4
>
> Attachments: WICKET-3596.patch
>
>
> When making simple ajax requests (apart from in chrome) using rc3 no response
> is being returned.
> Strangely enough, after making the request, and then refreshing the page
> everything is fine.
> The tomcat is producing this error:
> ERROR - DefaultExceptionMapper - Unexpected error occurred
> org.apache.wicket.behavior.InvalidBehaviorIdException: Cannot find behavior
> with id: 0 on component: [ [Component id = next]]
> at org.apache.wicket.Behaviors.getBehaviorById(Behaviors.java:299)
> at org.apache.wicket.Component.getBehaviorById(Component.java:4368)
> at
> org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:177)
> at
> org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:157)
> at
> org.apache.wicket.request.RequestHandlerStack.executeRequestHandler(RequestHandlerStack.java:84)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:205)
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:247)
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:138)
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:383)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:243)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:188)
> at
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:288)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> There are javascript errors on the page too:
> Error: [Exception... "'JavaScript component does not have a method named:
> "handleEvent"' when calling method: [nsIDOMEventListener::handleEvent]"
> nsresult: "0x80570030 (NS_ERROR_XPC_JSOBJECT_HAS_NO_FUNCTION_NAMED)"
> location: "<unknown>" data: no]
> Error: no element found
> Source File:
> http://localhost:8080/UniOrder/wicket/page?62-1.IBehaviorListener.0-wizard-form-buttons-next&random=0.9048021817669812
> Line: 1
> Error: no element found
> Source File: http://localhost:8080/UniOrder/?62
> Line: 1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
