tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk Sturzebecher" <dirk.sturzebec...@interface-ag.de>
Subject Component Disable Bug?
Date Wed, 26 May 2004 09:09:28 GMT

I have the following:

<property-specification name="submitFlag" type="boolean" initial-value="false"/>

<component id="cmdSubmit" type="Submit">
    <binding name="listener" expression="listeners.formSubmitListener"/>
    <binding name="selected" expression="submitFlag"/>
    <binding name="tag" expression="true"/>
    <binding name="disabled" expression="!dirtyFlag"/>   <!-- problem -->

in the formSubmitListener I have:


In this setup the if-block is never entered!

If I remove the line of the component marked with <!-- problem --> the if-block is being
executed, as intended.

Why is there a relation between the two? Why does the disable overwrite the tag? Is this intended?
How do I bypass this?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message