Disable pencil of RowEditor

[farshi114]

I need to disable row Editor in some rows(because of their specific data) I search too much but I can't find a way to do that.

I have two type of rows,rows with status A and rows with status B.

I want to enable pencil for rows A and disable for rows B

[andyba]

I don't think you can easily disable it but the rowEditor component does have the rendered attribute, try using that. If it causing a row based rendering according to a row based criteria then you will have pencils only in those rows which can be edited which pretty much follows common practice of only exposing controls when they can be used.

[farshi114]

i tried this code but it didn't work:
<p:column rendered="#{contract.status != "done"}">
<p:rowEditor />
</p:column>
(actualy 'B',is "Done")
Error is this:
javax.servlet.ServletException: Error Parsing /contract/index.xhtml: Error Traced[line: 250] Element type "p:column" must be followed by either attribute specifications, ">" or "/>".

[andyba]

i tried this code but it didn't work:
<p:column rendered="#{contract.status != "done"}">
<p:rowEditor />
</p:column>
(actualy 'B',is "Done")
Error is this:
javax.servlet.ServletException: Error Parsing /contract/index.xhtml: Error Traced[line: 250] Element type "p:column" must be followed by either attribute specifications, ">" or "/>".

Well your EL is wrong, use (note the use of code tags here)

Code: Select all

rendered="#{'done' ne contract.status}"

You have "done" quoted incorrectly which is what is causing the error.
Secondly you do not want to provisionally render the column because you can't.
You do this with the rowEditor component, like this

Code: Select all

<p:rowEditor rendered="#{'done' ne contract.status}"/>

Tip: rather than exposing such logic as an EL like this use your controller to determine this using a method....

Code: Select all

public boolean getRenderContractEditor(Contract contract) {
    return !"done'.equals(contract.getStatus());
}

and use it as follows

Code: Select all

<p:rowEditor rendered="#{contractController.renderContractEditor(contract)}"/>

The advantages with this approach are many

- You only need to implement this logic in one place but use the result of the method call in many places (satisfies the DRY principle)
- Places the responsibility for this with the contract controller where it belongs (Satisfies the S in SOLID)

There are others as well.

[farshi114]

thanks...it's work