[richfaces-issues] [JBoss JIRA] Commented: (RF-10397) ComponentIdResolver does not resolve id for prependId="false" correctly

[Martin Kočí (JIRA)]

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

Martin Kočí commented on RF-10397:
----------------------------------

Btw. both JSF implementations (mojarra, myfaces) don't say anything if visit ids dont match a component. I don't know if that is expected behaviour and I raised https://issues.apache.org/jira/browse/MYFACES-3019.
What opinion has RichFaces team about that? 

> ComponentIdResolver does not resolve id for prependId="false" correctly
> -----------------------------------------------------------------------
>
>                 Key: RF-10397
>                 URL: https://issues.jboss.org/browse/RF-10397
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: base functionality 
>    Affects Versions: 4.0.0.Milestone5
>         Environment: Richfaces 4.0 trunk svn.rev 21378, mojarra 2.0.3
>            Reporter: Martin Kočí
>            Priority: Minor
>
> <h:form id="formId" prependId="false">
>   <h:inputText id="inputText1" />
>   <h:inputText id="inputText2" >
>     <a4j:ajax event="valueChange" execute=":formId:inputText1" />
>   </h:inputText>
> </h:form>
> will not execute component id="inputText1". I found that ComponentIdResolver at line 179 contains:
> clientId = SEPARATOR_CHAR_JOINER.join(topMatchComponent.getClientId(facesContext), id.substring(idx + 1));
> But in this case topMatchComponent is HtmlForm with prependId="false" and spec says that "children of this UIForm instance in the view have the form's clientId prepended to their clientIds if and only if the form's prependId property is true".
> so richfaces resolve this clientId as "formId:inputText1", but it should be only "inputText1" in this case
> There are similar bugs registered already, but some of them are closed and some not so I can say if it is same problem. Sorry for possible duplicity.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira