To my knowledge, that's expected behavior: rendered=false makes a component inert in all phases.


On 2 Aug 2005, at 4:09, [EMAIL PROTECTED] wrote:

<h:commandButton value="Cancel" immediate="true" action="#{myBacker.myMethod}"  rendered="#{myBacker.editMode}" />

myBacker is a request scoped managed bean.

When the button is clicked, the backing bean is created, but myMethod does not fire.  The runtime will not complain if @action is set to myBacker.myNonExistMethod .  

The method will fire if true is the literal value of @rendered, or if the editMode property is set to true in the constructor.

It appears as though the action will not fire, if the rendered expression evaluates to false.
Can anyone explain otherwise?  More importantly, can someone educate me as to why this is a good idea?

Dennis Byrne

<x-tad-smaller>Met vriendelijke groeten,

Jan Dockx
</x-tad-smaller><x-tad-smaller>
PeopleWare NV - Head Office</x-tad-smaller>
<x-tad-smaller>
Cdt.Weynsstraat 85
B-2660 Hoboken
Tel: +32 3 448.33.38
Fax: +32 3 448.32.66 </x-tad-smaller>
<x-tad-bigger>
</x-tad-bigger>
<x-tad-smaller>
PeopleWare NV - Branch Office Geel</x-tad-smaller>
<x-tad-smaller>
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25</x-tad-smaller>
<x-tad-bigger>
</x-tad-bigger>
<x-tad-smaller>
http://www.peopleware.be/
</x-tad-smaller><x-tad-smaller>http://www.mobileware.be/</x-tad-smaller>

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to