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 FieldTranslate instance at runtime.
You are probably more familiar with the prop: binding which can access a
property at runtime.
On 16 May 2014 18:02, "Michael Wyraz" <michael.wy...@evermind.de> wrote:
> 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<Object> translate;
>
> @Parameter(defaultPrefix = BindingConstants.VALIDATE)
> @SuppressWarnings("unchecked")
> private FieldValidator<Object> validate;
>
> But the type of the default() methods differ:
>
> final Binding defaultTranslate()
> {
> return defaultProvider.defaultTranslatorBinding("value",
> resources);
> }
>
> final Binding defaultValidate()
> {
> return defaultProvider.defaultValidatorBinding("value",
> resources);
> }
>
> The interfaces "Binding" and "FieldTranslator" have nothing common. So I
> cannot imagine that (and how) this could work.
>
> Is it a bug?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: dev-h...@tapestry.apache.org
>
>
