You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Cagatay Civici (JIRA)" <de...@myfaces.apache.org> on 2007/01/12 20:11:27 UTC
[jira] Resolved: (TOMAHAWK-848) FacesIO is not working with the
latest DOJO updates
[ https://issues.apache.org/jira/browse/TOMAHAWK-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cagatay Civici resolved TOMAHAWK-848.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.5-SNAPSHOT
I've updated the dojo api used in FacesIO extension to be compatible with the 0.4.x. In addition when FacesTransport is loaded and added to dojo.io.transports, I've set it as the first transport in the available transports lists(dojo.io.transports) otherwise plain XMLHTTPTRANSPORT was used for the ajax request resulting FacesTransport to be ignored. With this components like inputsuggestajax and tablesuggestajax are working again when state saving is set to client mode.
> FacesIO is not working with the latest DOJO updates
> ---------------------------------------------------
>
> Key: TOMAHAWK-848
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-848
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Affects Versions: 1.1.5-SNAPSHOT
> Reporter: Cagatay Civici
> Assigned To: Cagatay Civici
> Fix For: 1.1.5-SNAPSHOT
>
>
> Beginning from dojo version 0.3.x, FacesIO started to fail and ajax components stopped working when state saving is set to client side.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira