You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Volker Weber (JIRA)" <de...@myfaces.apache.org> on 2006/09/25 12:31:50 UTC
[jira] Created: (TOBAGO-137) Tree on a Tab panel breaks
switchtype=reloadTab functionality
Tree on a Tab panel breaks switchtype=reloadTab functionality
-------------------------------------------------------------
Key: TOBAGO-137
URL: http://issues.apache.org/jira/browse/TOBAGO-137
Project: MyFaces Tobago
Issue Type: Bug
Reporter: Volker Weber
Fix For: 1.0.9
A tabgroup with switchtype=reloadTab (ajax reloading) always decodes the first tab,
this fails if a tree is on the first tab, but another tab was submitted.
This is a problem of the viewId sequence.
A ajax request should store the view under the same sequenceId that the restored view was.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TOBAGO-137) Tree on a Tab panel breaks
switchtype=reloadTab functionality
Posted by "Volker Weber (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TOBAGO-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Volker Weber resolved TOBAGO-137.
---------------------------------
Resolution: Fixed
Can't reproduce this problem, may be fixed during working on TOBAGO-167 (replacing jsf state on ajax requests)
> Tree on a Tab panel breaks switchtype=reloadTab functionality
> -------------------------------------------------------------
>
> Key: TOBAGO-137
> URL: https://issues.apache.org/jira/browse/TOBAGO-137
> Project: MyFaces Tobago
> Issue Type: Bug
> Reporter: Volker Weber
> Assigned To: Volker Weber
> Fix For: 1.0.10
>
>
> A tabgroup with switchtype=reloadTab (ajax reloading) always decodes the first tab,
> this fails if a tree is on the first tab, but another tab was submitted.
> This is a problem of the viewId sequence.
> A ajax request should store the view under the same sequenceId that the restored view was.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.