]
Brian Leathem commented on RF-13317:
------------------------------------
[~lfryc] have you yet pushed your changes to github? Can you link to the branch here?
I see this branch:
However
the last commit there is for the PoC workaround with the com.sun class.
ExtendedPartialViewContextImpl should specify correct
javax.faces.ViewState id in startUpdate()
-----------------------------------------------------------------------------------------------
Key: RF-13317
URL:
https://issues.jboss.org/browse/RF-13317
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.3.4
Environment: Wildfly-8.0.0.Beta1, jsf-impl-2.2.3-jbossorg-1
Reporter: Matti Bickel
Assignee: Lukáš Fryč
Priority: Critical
Labels: jsf22
Fix For: 4.3.5, 5.0.0.Alpha3
I'm using several {{<rich:autocomplete>}} fields in a {{<h:form>}}, but
have noticed the issue with several other AJAX requests:
When the response comes back, the data is fine but I get a JSF error saying
bq. During update: javax.faces.ViewState not found
Following that, no componentData is available to the Autocomplete component and no
suggestions get displayed.
For reference the [javadoc for
ResponseStateManager.VIEW_STATE_PARAM|https://javaserverfaces.java.net/no...]
says:
{quote}
Implementations must use this constant field value as the name of the client parameter in
which to save the state between requests. The id attribute must be a concatenation of the
return from UIComponent.getContainerClientId(javax.faces.context.FacesContext), the return
from UINamingContainer.getSeparatorChar(javax.faces.context.FacesContext), this constant
field value, the separator char, and a number that is guaranteed to be unique with respect
to all the other instances of this kind of client parameter in the view.
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: