--- Begin Message ---
Hi Apurva,
 
Yes I fully agree with what Danny has suggested.
 
you were doing it like this:
 
<tr:commandButton inlineStyle="x6m xag" text="Edit"
action="#{EditCusLinksBB.editAssoCE}"
rendered="#{editCustBB.certifiedEntity != null and
EditCusLinksBB.corpEditable}" />
 
So the problem comes with the rendered attribute where you are checking for 
null.  Since it is a new request, you could try apply pageflow scope to 
accessor methods of certifiedEntity (as it calls the getCertifiedEntity) and it 
is always reset with each request.
 
 
regards,
Anshuman


________________________________

From: Mistry, Apurva [mailto:[EMAIL PROTECTED]
Sent: Tue 2/13/2007 10:18 PM
To: adffaces-user@incubator.apache.org
Subject: RE: Problem with action attribute in jsf commandbutton



Forgot to mention this....
If I add the bean in session scope in faces-config, the action is called upon.
however i required it to be in request scope. Why would it work in session and 
not request.
thanks

-----Original Message-----
From: Mistry, Apurva [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 13, 2007 11:14 AM
To: adffaces-user@incubator.apache.org
Subject: Problem with action attribute in jsf commandbutton


Hi,
I am having the problem with action attribute with trinidad
commandbutton link.
I have two action buttons, edit and update. Edit is visible first when
the page is loaded with the 4 related fields in read-only mode.

When the user clicks Edit button, a flag is set in backing bean to
render the Update button instead of Edit, and the fields are editable.
However, when the Update button is clicked, to update the modified data,
the binded action is not called.

 
The backing bean for these actions is in request scope, and as far as I
know, anytime the request is made the corresponding backingbean object
instance is created and the action is performed. After the request is
serviced, that instance is killed.

I am not sure why is the action is not called upon.
Below is the code snippet.
I would appreciate any help.

<tr:commandButton inlineStyle="x6m xag" text="Edit"
action="#{EditCusLinksBB.editAssoCE}"
rendered="#{editCustBB.certifiedEntity != null and
EditCusLinksBB.corpEditable}" />

<tr:commandButton inlineStyle="x6m xag" text="Update"
action="#{EditCusLinksBB.updateAssoCE}"
rendered="#{!EditCusLinksBB.corpEditable}"/>

 

thanks
apurva.

*********************************************************************
 Confidentiality Notice:  This email message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
 confidential and privileged information. Any unauthorized review, use,
 disclosure or distribution is prohibited. If you are not the intended
 recipient, please contact the sender by email and destroy all copies of
the original message.
*********************************************************************

*********************************************************************
  Confidentiality Notice:  This email message, including any attachments,
  is for the sole use of the intended recipient(s) and may contain
  confidential and privileged information. Any unauthorized review, use,
  disclosure or distribution is prohibited. If you are not the intended
  recipient, please contact the sender by email and destroy all copies of
  the original message.
*********************************************************************


<<winmail.dat>>


--- End Message ---
Disclaimer

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom it is addressed.  If you 
have received this communication in error, please immediately notify the [EMAIL 
PROTECTED] and destroy the original message. The recipient should check this 
email and any attachments for the presence of viruses.  Ness has taken every 
reasonable precaution to minimize this risk, and accepts no liability for any 
damage caused by any virus transmitted in this email.  Ness reserves the rights 
to monitor and review the content of all messages sent to or from this E-mail 
address, and store them on the Ness E-mail system.

Reply via email to