CODEWITHSUNDEEP
javajsfprimefaces
Seitaridis
Seitaridis

Reputation: 4529

Update component without specifying the absolute client id

The code fragment below represents an editor. In my application, a windows displays a group of editors in a tab panel, each tab containing a datatable with the editors as rows. When a node is selected, its text will be displayed in the organizationUnit input text. The editor shouldn't know about it's parents. Is it possible to update organizationUnit without using the absolute client id?

<p:tabView value="#{accountsBean.groups}" var="group">
    <p:tab title="#{eval.getString(group.name)}">
        <p:dataTable value="#{group.editors}"
            var="editor">                       
            <p:column>
                 <custom:include src="#{editor.component}">
                     <ui:param name="bean" value="#{editor.beanName}"/>
                     <ui:param name="mandatory" value="#{editor.mandatory}"/>
                     <ui:param name="name" value="#{editor.name}"/>
                 </custom:include>
            </p:column>
        </p:dataTable>
    </p:tab>                        
</p:tabView>

<h:panelGrid id="containerEditor" columns="2">
    <h:outputText value="#{name}: #{mandatory ? '*' : ''}" />
    <p:tree value="#{bean.root}" var="node" selectionMode="single" selection="#
        {selectedNode}">
        <p:ajax event="select" listener="#{bean.onNodeSelect}"
            update="update_organization_unit" immediate="true" />
        <p:treeNode>
            <h:outputText value="#{node}" />
        </p:treeNode>
    </p:tree>
    <h:outputText />
    <p:inputText id="organizationUnit" value="#{bean.selectedItemPath}"
        disabled="true" />
</h:panelGrid>

The tab panel is inside a form called form with prependId="false"

Upvotes: 0

Views: 1331

Answers (2)

siebz0r
siebz0r

Reputation: 20329

A common 'trick' I use to avoid refering to ids is to use binding.

Example:

<h:form>
    <p:button binding="#{button}" ...
</h:form>

....
<p:button update=":#{button.clientId}" ...

Note: This doesn't work for some tags like h:outputText that don't generate an id.

Upvotes: 1

RinaldoDev
RinaldoDev

Reputation: 995

When you have components inside different NamingContainers, and those are not nested**, you must use absolute client id.

In your case, if you don't use the separator character at the begining, the findComponent algorithm would search up until it finds a NamingContainer: this would be your p:tree. Then it would try to find the component inside the p:tree, since it's not there, the exception you mentioned is thrown.

On the other hand, If you do use the separator character at the begining, you must use the absolute client id.

Short answers: No. Unless you change the way your components are organized, you can't update organizationUnit without using the absolute client id.

** If NamingContainers are nested, components inside the outter NamingContainer may update ones inside an inner NamingContainer by referencing their id before the id of the actual component they want to update, for example: update="innerContainer1Id:componentId", or even update="innerContainer1Id:innerContainer2:componentId".

Algorithm is explained in the JavaDoc.

Upvotes: 1

Related Questions