[
https://issues.apache.org/jira/browse/MYFACES-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr reopened MYFACES-2598:
------------------------------------
Assignee: Jakob Korherr (was: Leonardo Uribe)
Leonardo,
UIViewParameter has to get a valid clientId here, otherwise the state saving
for the parameter does not work correctly and this causes the problem that you
are not able to use postbacks on a view with at least one required
UIViewParameter.
I first reopened MYFACES-2592, because I thought this was the problem, but it
turns out that this issue is the problem.
> UIViewParameter does not get an automatic id
> --------------------------------------------
>
> Key: MYFACES-2598
> URL: https://issues.apache.org/jira/browse/MYFACES-2598
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.0.0-beta-3
> Reporter: Jakob Korherr
> Assignee: Jakob Korherr
> Fix For: 2.0.0-beta-3
>
>
> You see the fancy missing id warning when using f:viewParam:
> 10.03.2010 13:35:36 javax.faces.component.UIComponentBase getClientId
> WARNUNG: WARNING: Component j_id12 just got an automatic id, because there
> was no id assigned yet. If this component was created dynamically (i.e. not
> by a JSP tag) you should assign it an explicit static id or assign it the id
> you get from the createUniqueId from the current UIViewRoot component right
> after creation! Path to Component: {Component-Path : [Class:
> javax.faces.component.UIViewRoot,ViewId: /viewparam.xhtml][Class:
> javax.faces.component.UIPanel,Id: javax_faces_metadata][Class:
> javax.faces.component.UIViewParameter,Id: j_id12]}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
