Hi all,
I'm finally getting around to upgrading my 3.0 codebase and things are
going spectacularly! However, I have a case where it seems the new
component parameter handling isn't doing what I would like it to (it's a
rare case-- almost all others make much more sense now!), and I was
wondering if others had encountered similar issues.
Basic idea:
I have a search component that takes a default value for a search field
(so the user will have some info pre-filled out for them) as a
parameter. In Tapestry 3.0, this was specified as an 'in' parameter,
and the property generated by the parameter was also used to bind the
text the user had typed when the search form was submitted. It looked
approximately like this:
SearchComponent.html:
<form jwcid="@Form"....>
Group Name: <input jwcid="@TextField" value="ognl:groupName"/>.........
</form>
SearchComponent.jwc:
<component....>
<parameter direction="in" name="groupName" type="java.lang.String"
required="no" default-value="null"/>
</component>
With Tapestry 4, however, since I am using the groupName as the search
field property as well as the parameter, it is attemping to write back
the user-submitted value to the page that is binding the parameter. In
this case, that is *not* desired behavior. I can easily work around
this by creating a separate property for the search field value, but
would rather not if it is avoidable.
Has anyone else encountered this? If so, how did you solve it?
Thanks,
Danny
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
