|
Hi, I think there are is a bug in commandLink in treating
the “rendered” attributes. Below is a demonstration. The jsf page concerned is
to have an ‘edit’ more and a ‘browse’ mode. When the
page is in edit mode the ‘Save Changes’ and ‘Cancel’
button will show, else the ‘Edit’ and ‘Back’ button
will show. The rendering of the buttons are OK, however as
it stands the ‘Save Changes’ and ‘Cancel’ button will
not trigger the backing bean action. If I take away the rendered=”…”
attributes I will see all 4 buttons, but everything works as expected. ------------------------------------------------------------------------- <h:commandLink value="Edit" action="#{userBean.editUserAction}" rendered="#{!userBean.isEdit}"> </h:commandLink> <f:verbatim>  </f:verbatim> <h:commandLink value="Back" action="#{userBean.backAction}" rendered="#{!userBean.isEdit}"> </h:commandLink> <h:commandLink value="Save Changes" action="#{userBean.saveAction}" rendered="#{userBean.isEdit}"> </h:commandLink> <f:verbatim>  </f:verbatim> <h:commandLink value="Cancel" action="#{userBean.backAction}" rendered="#{userBean.isEdit}"> </h:commandLink> Is there a work
around for this? Thanks Yee |
- Bugs with commandLink rendered="..." Yee CN
- Re: Bugs with commandLink rendered="..." Martin Marinschek
- RE: Bugs with commandLink rendered="...&qu... Yee CN
- Re: Bugs with commandLink rendered="..... Martin Marinschek

