ציטוט Kent Tong:
Ron Piterman <mplayer <at> vollbio.de> writes:
in a component I have a 'required' parameter, which is passed to a
validator bean to use in a "ValidField" component:
<parameter name="required" default-value="false">
...
<bean...>
<set name="required" value="required">
If i use more than one instance of my component in a page, the bean is
not updated for each instance, thus all are either required or not,
depending on the *first* instance.
<set ...> is setting a value to the "required" property
of the bean (one off). It is NOT binding the "required"
property to an OGNL expression, therefore changing to
your "required" parameter will not be seen by the "required"
property.
Please look at the example in bug
http://issues.apache.org/jira/browse/TAPESTRY-406
It shows that if you use 3 components of the same type, each one has a
bean, whose attribute is set to a parameter of the component, the
*first* component's parameter will apply to all 3 beans. Thats very
strange, as if the three instances share the same bean without updating
its properties.
--
Author of e-book for learning Tapestry (www.agileskills2.org/EWDT)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
