Ron Piterman wrote:
Hi,
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.
Is this a bug, or should bean properties not be minupulated through
parameters? or maybe it is the result of removing the "direction"
attribute from the parameter definition?
Cheers,
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Is this somehow related to the bug below I reported this morning? In my
case if the an attribute on an html tag is set, it won't override it.
TAPESTRY-403
I have a contrib:tableRows component that binds the EvenOdd class like
this:
<component id="tableRows" type="contrib:TableRows">
<binding name="class" expression="beans.evenOdd.next"/>
<binding name="row" expression="currentRow"/>
</component>
However the evenOdd class was never getting instantiated/processing on
each row in the table.
I looked into my .html page and noticed that I had something like this:
<tr jwcid="tableRows" class="odd">
but when I took the class attribute out of my html the evenOdd bean got
instantiated and processing. So it looks like there is an issue of
binding a bean to an attribute if it already exists in a .html page.
This page is part of an app I am migrating from 3.0, in which the
evenOdd bean processed properly with the class attribute in the .html page.
Is this an issue with contrib:tableRows or bindings in general if you
attempt to bind to an html attribute that is already set?
--
Scott F. Walter Scott F. Walter
Principal Consultant
Vivare, Inc.
E: [EMAIL PROTECTED]
E: [EMAIL PROTECTED]
Visit scottwalter.com <http://scottwalter.com> --Point. Click. Explore!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
