[
https://issues.apache.org/jira/browse/MYFACES-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Werner Punz resolved MYFACES-2855.
----------------------------------
Fix Version/s: 2.0.2-SNAPSHOT
Resolution: Fixed
Ok after testing it with the data table where this issue is the only one where
it could cause errors bevause of the auto id counter mechanisms, I think it is
safe to commit now (btw. according to others exactly this auto execute id
causes problems in the mojarra table by pushing the row id automatically into
the ajax cycle with every command link which ajaxes)
> jsf.js: execute id difference between myfaces and mojarra
> ---------------------------------------------------------
>
> Key: MYFACES-2855
> URL: https://issues.apache.org/jira/browse/MYFACES-2855
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Reporter: Werner Punz
> Fix For: 2.0.2-SNAPSHOT
>
>
> <h:panelGroup id="bla">
> <h:inputText id="inputbla"
> value="#{myBean2.searchTerm}" />
> <h:commandLink value="Press me for more action"
> action="#{myBean2.doSearch}">
> <f:ajax execute="bla" render="content"/>
> </h:commandLink>
> </h:panelGroup>
> causes following output in mojarra
> form2 form2
> form2:inputbla
> javax.faces.ViewState 6697453697014869722:-1090088301633916042
> javax.faces.behavior.even... action
> javax.faces.partial.ajax true
> javax.faces.partial.event click
> javax.faces.partial.execu... form2:j_idt8 form2:bla
> javax.faces.partial.rende... form2:content
> javax.faces.source form2:j_idt8
> in myfaces
> form2:inputbla
> form2_SUBMIT 1
> javax.faces.ViewState
> EmWJgKYkJoTEWDCzpUwZQR3Ek94rGnxK1V6NEZgO6yDgPANeOc1wplJjDYezu2cx9aQ7ZSKNPyGY
> L8P9y5DwH2codFvGPjklD04wuxG4XXTPutNww3pdzIsMkw0=
> javax.faces.behavior.even... action
> javax.faces.partial.ajax true
> javax.faces.partial.event click
> javax.faces.partial.execu... form2:bla
> javax.faces.partial.rende... form2:content
> javax.faces.source form2:j_id1980473354_760ba132
> as it seems mojarra also passes the id/name of the issuing element into
> execute per default, I have to check the spec if this is correct
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
