On Thu, 06 Jan 2011 08:09:41 -0200, Paul Stanton <p...@mapshed.com.au>
wrote:
On 6/01/2011 12:53 PM, Thiago H. de Paula Figueiredo wrote:
As far as I know, when you return a MultiZoneUpdate, the value passed
to the zone parameter is completely ignored, so there's no need to
create a dummy zone.
really? i thought a valid zone was required to initiate the ajax request
(in the current methodology).
A valid zone is needed for MultiZoneUpdate requests AFAIK, but which one
is passed to the zone parameter is ignored.
Tapestry.findZoneManagerForZone(zoneId).updateFromURL(url)
Do you give us permission to use it in Tapestry itself if the team
approves your code?
absolutely. only glaringly obvious problem is that the context
parameters don't get encoded properly, hopefully someone can rectify
this..
Cool!
Feel free to file a JIRA for your suggestions.
I will do.
I'd be keen to contribute further, but I imagine I don't understand the
big picture well enough yet to be a committer.
Give your suggestions and let the Tapestry team decide. :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
