[richfaces-issues] [JBoss JIRA] (RF-11763) javascript error : item is undefined on nested tabPanel with switchType='ajax'

[Jean ANDRE (JIRA)]

    [ https://issues.jboss.org/browse/RF-11763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677011#comment-12677011 ] 

Jean ANDRE edited comment on RF-11763 at 3/15/12 11:16 AM:
-----------------------------------------------------------

Hell guys,

We have the pleasure to announce you that we have found the root cause of the problem early this morning. The problem is caused by the <rich:message> tag inside the searchClient.xhtml file.

{code}
     <!--              -->
     <!--  SEARCH !    -->
     <!--              -->
     <h:commandButton id="doSearchCmd"
       value="#{msg['search.command.search']}"
       action="#{searchClientController.doSearch}" />
    </div>
    <p><rich:message for="doSearchCmd" /></p>
  </a4j:outputPanel>
</ui:composition>
{code}

To make the story short, the search screen was developed first, later we have implemented the nested tabs but the tabPanel did not work at all since the beginning. Then we thought it was a bug from the tabPanel and we reported the bug several months ago without testing the tapPanel outside our application (time constraint). Few days ago, we took thetime to test the tabPanel outside the application (see the workbench application) and we saw that nested tabPanel is running pretty well. Based on this fact, we decided to go deeper for trapping the bug by pruning unnecessary element, because this bug was a show stopper for us at this point of time of the project.

Thank you to keep us inform about the real reason about this situation. Why a <rich:message> have an impact on tab switching.

*Note 1:* replace <rich:message> by a <h:messages /> works but we have to customized the layout.

Best regards,





 
                
      was (Author: jorelia64):
    Hell guys,

We have the pleasure to announce you that we have found the root cause of the problem early this morning. The problem is caused by the <rich:message> tag inside the searchClient.xhtml file.

{code}
     <!--              -->
     <!--  SEARCH !    -->
     <!--              -->
     <h:commandButton id="doSearchCmd"
       value="#{msg['search.command.search']}"
       action="#{searchClientController.doSearch}" />
    </div>
    <p><rich:message for="doSearchCmd" /></p>
  </a4j:outputPanel>
</ui:composition>
{code}

To make the story short, the search screen was developed first, later we have implemented the nested tabs but the tabPanel did not work at all since the beginning. Then we thought it was a bug from the tabPanel and we reported the bug several months ago without testing the tapPanel outside our application (time constraint). Few days ago, we took thetime to test the tabPanel outside the application (see the workbench application) and we saw that nested tabPanel is running pretty well. Base on this fact, we decided to go deeper for trapping the bug by pruning unnecessary element, because this bug was a show stopper for us.

Thank you to keep us inform about the real reason about this situation. Why a <rich:message> have an impact on tab switching.

*Note 1:* replace <rich:message> by a <h:messages /> works but we have to customized the layout.

Best regards,





 
                  
> javascript error : item is undefined on nested tabPanel with switchType='ajax'
> ------------------------------------------------------------------------------
>
>                 Key: RF-11763
>                 URL: https://issues.jboss.org/browse/RF-11763
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.1.0.CR1
>         Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use @Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1) - AspectJ 1.6.12 / AJDT 
>            Reporter: Jean ANDRE
>            Priority: Blocker
>             Fix For: 4.Future
>
>         Attachments: RF-11763Web.zip, RF-11763_ScreenShot.png, RF-11763_ScreenShot_malformedXML.png, RF-11763_ScreenShot_malformedXML.xml, RF-11763_ScreenShot_Undefined.png, screenshot-1.jpg
>
>
> See also RF-11750 for the context.
> Briefly, we have nested tabPanel - The firs tabPanel is made of static and dynamic tabPanel. One tabPanel contains the search form. When the user performs a search and for each search we open a new tab that contains the result list. When the user click on an item, we update the tab with the detailed information.
> The detailed information is made of 6 tabs - There are like a subtabs from the parent tabs. When we set the switchType to 'client' the tab performs well. But as we want that the same tab serves as form to edit and view the detailed information, we want to refresh the tab to display the inputText instead of the outputText. This is the edit mode.
> Then, we need to refresh the tab and we decided to pass in ajax switchType for theses subTab. Owener, switching to the 'ajax' triggers a javascript error that blocks the UI. None tab is selectable, user cannot switch from a tab to another tab. Moreover we failed to refresh the tab but the reason is still unknown.
> Javascript error is :
> {code}
> item is undefined - [Stopper sur une erreur] if (!item.disabled && item.getName() === itemName) { 
> toggle...chfaces (ligne 363)
> http://localhost:12000/crm/javax.faces.resource/togglePanel.js.jsf?ln=org.richfaces
> {code}
> The involved code is (where >>>> is):
> {code}
> /**
> * @private
> * */
> __getItemIndex : function (itemName) {
> var item;
> for (var i = 0; i < this.items.length; i++) {
>   item = this.items[i];
> >>>>>> if (!item.disabled && item.getName() === itemName) {
> return i;
> }
> }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira