[
https://issues.apache.org/jira/browse/WICKET-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523733
]
Carlos Pita commented on WICKET-905:
------------------------------------
One more remark: replacing the onHide behavior callback with a custom handler
that does a GET httpxmlrequest or prototype ajax.request to the same -fixed-
url, and then parses the response in an adhoc way, lets me do succesive ajax
requests without raising the 0x80004005 error. It seems to be something
involving firefox and wicket management of ajax requests, maybe it's related to
the abort call that's done on the transport, dunno.
> [nsIXMLHttpRequest.open] nsresult: 0x80004005 after calling behavior from
> iframe
> --------------------------------------------------------------------------------
>
> Key: WICKET-905
> URL: https://issues.apache.org/jira/browse/WICKET-905
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta3, 1.3.0-beta4
> Reporter: Carlos Pita
> Attachments: iframe.tgz
>
>
> Below is a description copy pasted from the irc channel. Please take into
> account that you must mount the attached example at a depth-2 path (as
> <context>/<app>/iframe/wicket) or otherwise fix the url from
> hideBehavior.getCallback().replace("../", "") (line 60 of WicketAjaxPage, I
> don't know of a better way of doing this, adding the behavior to the iframe
> doesn't work either).
> >igor, do you remember that a couple of days ago i asked you about calling an
> >ajax behavior from an iframe?
> >i managed to do it using a vanilla XmlHttpRequest to reenter wicket through
> >the behavior and then parsing the wicket response "by hand"
> > but i tried a lot of combinations to avoid that hack to, the closer i got
> > was patching the behavior url a bit, to get it relative to the main page,
> > not the iframe, and spitting out a bit of javascript on the top window to
> > be called by the iframe
> > the behavior is executed and the ajax reponse is correctly handled, but
> > then every other ajax request fail
> > with this: uncaught exception: [Exception... "Component returned failure
> > code: 0x80004005 (NS_ERROR_FAILURE) [nsIXMLHttpRequest.open]" nsresult:
> > "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: javascript:
> > eval(__firebugTemp__); :: anonymous :: line 1" data: no]
> > I have a quickstart for this, do you think it's a bug in wicket?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
