Yes, the ability to disambiguate parameters in this way has always been present.
On Thu, Apr 14, 2011 at 8:50 AM, Dmitriy Vsekhvalnov
wrote:
> works like a charm. thanks.
>
> Is it backward compatible with 5.1.0.5 (i mean zoneupdater.zone='whatever')
> ?
>
> On Thu, Apr 14, 2011 at 7:30 PM, Taha
works like a charm. thanks.
Is it backward compatible with 5.1.0.5 (i mean zoneupdater.zone='whatever')
?
On Thu, Apr 14, 2011 at 7:30 PM, Taha Hafeez wrote:
> Hi
>
> In 5.1.0.6 a parameter zone was added to Select. So in your case both
> Select
> component and mixin ZoneUpdater have 'zone' as p
Hi
In 5.1.0.6 a parameter zone was added to Select. So in your case both Select
component and mixin ZoneUpdater have 'zone' as parameter.In tapestry, if
both component and mixin have the same parameter name, the parameter is
assigned to the component and mixin does not get the parameter.
As ZoneU
Hi all,
just upgraded application to 5.1.0.8-SNAPSHOT, and got weird error for
components that includes ZoneUpdater (
http://tinybits.blogspot.com/2010/03/new-and-better-zoneupdater.html)
org.apache.tapestry5.ioc.internal.util.TapestryException: Parameter(s)
'ZoneUpdater.zone' are required for
o
