Hi Michael, in future... Please post to the user's mailing list. This list
is for the tapestry development team.
No, this is not a bug. Pages and components are singletons. Under the hood
they use bindings to get() and set() dynamic values at runtime. In this
instance the binding can get() a Field
Not a bug. Defaults are allowed to supply either a literal default or a
binding. The binding's "get" will evaluate to an object of the proper type.
In fact, if memory serves, when you supply a literal value, tapestry wraps that
in a "literal binding" anyway, because under the hood, all of thos
Hi,
I found something I do not understand and which is probably a bug. From
org.apache.tapestry5.corelib.base.AbstractTextField:
@Parameter(required = true, allowNull = false, defaultPrefix =
BindingConstants.TRANSLATE)
private FieldTranslator translate;
@Parameter(defaultPrefix
