Thank you.
This should facilitate the migration of our components in 5.2.
I just created a jira for https://issues.apache.org/jira/browse/TAP5-1415
Best Regards
François
2011/1/15 Howard Lewis Ship
> This was a bit of unintended consequences ... the Mixin's zone
> parameter was ignored and the
This was a bit of unintended consequences ... the Mixin's zone
parameter was ignored and the Select components (new in 5.2) zone
parameter was bound itstead. Using zoneupdater.zone="searchZone",
which is Tapestry's way of identifying, in the template, that its the
zone parameter of the ZoneUpdater
Thank you so much Josh
I should have read the release notes more carefully.
http://tapestry.apache.org/release-notes-520.html
more precisely
https://issues.apache.org/jira/browse/TAP5-138
Regards
François
2011/1/14 Josh Canfield
> /**
> * Binding the zone parameter will cause any change o
/**
* Binding the zone parameter will cause any change of Select's
value to be handled as an Ajax request that updates
* the
* indicated zone. The component will trigger the event {@link
EventConstants#VALUE_CHANGED} to inform its
* container that Select's value has changed.
Hi all
Do you see any raison that could explain why tapestry
search this kind of parameter in the form?
Where is this strategie dfine?
Regards
François
Le 10 janvier 2011 14:09, Facon François a
écrit :
> in Jumpstart the page
> http://jumpstart.doublenegative.com.au/jumpstart/examples/javasc