CONNER, BRENDAN (SBCSI) wrote the following on 9/9/2005 4:00 PM:
Can you take out the globalOnly attribute in your <h:messages> tag in
your JSP? Maybe it's getting some error which is causing the form to be
redisplayed.
I commented that out and still not getting insertAction to be hit.
Doesn't 'rendered' just decide whether or not to display the component?
I can't see why using the rendered attribute would cause the action
event to not fire when the button is clicked?
Unless maybe like Mike was possibly eluding to - that when the form
submits it tries to see if the rendered value is still true (and
possibly in this case it isn't?). If that's the case I don't really
understand the logic behind implementing it that way. But I'm not sure
that's the problem though.
- Brendan
-----Original Message-----
From: Rick Reumann [mailto:[EMAIL PROTECTED]
Sent: Friday, September 09, 2005 2:56 PM
To: MyFaces Discussion
Subject: Re: understanding the impact of 'rendered'
CONNER, BRENDAN (SBCSI) wrote the following on 9/9/2005 3:28 PM:
It would be interesting to see whether reversing the order of your
buttons results in the reverse outcome. In other words, if you
specify:
then it would be interesting to see if that makes the update action
inoperable. If that is the case, then something is being rendered
even
for the "unrendered" button that is somehow messing up how the page
gets
submitted for the "rendered" button.
It's just so weird. I pasted the form I have here:
http://rafb.net/paste/results/vYp8Zi19.html
I removed all buttons so that I only have this one:
<h:commandButton type="submit" id="insert" value="INSERT THIS EMPLOYEE"
action="#{employeeAction.insertAction}"
rendered="#{!employeeAction.editMode}"/>
Click on above button, page just reloads. insertAction not reached.
If I remove the rendered:
<h:commandButton type="submit" id="insert" value="INSERT THIS EMPLOYEE"
action="#{employeeAction.insertAction}"/>
Click on above button, insertAction *is* reached.
I'm baffled.
--
Rick
