You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/03/15 19:21:29 UTC
[jira] Created: (TAP5-1476) Deprecate MultiZoneUpdate, replace with
an injectable service to collect zone updates
Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
-------------------------------------------------------------------------------------
Key: TAP5-1476
URL: https://issues.apache.org/jira/browse/TAP5-1476
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.3.0
Reporter: Howard M. Lewis Ship
MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
I'd like to see something like:
@Inject
private ZoneUpdater zoneUpdater();
Object onSuccess()
{
zoneUpdater.update("foo", fooBlock);
zoneUpdater.update("bar", barBlock);
return myZone.getBody();
}
The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by Howard Lewis Ship <hl...@gmail.com>.
The JavaScript is a bit in flux right now; I'm gradually creating new
stable APIs under the T5 namespace, along with a publish/subscribe
system to let components work together without explicit binding. In
any case, this effort will continue past 5.3 and into 5.4.
That's not an answer, it's just a promise that in 5.4 it will be very,
very easy to do what you want.
On Thu, Jul 28, 2011 at 2:14 AM, Denis Stepanov
<de...@gmail.com> wrote:
> Hi,
>
> It would be nice if there was a way how to trigger a multi zone update on the client side, waiting for all zone updates to render in one request could take too long and sometimes it's better to display refreshing zones to the user.
Well, you could have a Zone render a ProgressiveDisplay component
around your content, that will defer the expensive rendering to yet
another request.
>
> Our simple implementation returns JS code which then triggers zone updates, because of that it would be nice to have a default event from the Zone component to refresh its content, also there could be a "pregressive" parameter which will load it's content after render and it will eleminate the need for the PregressiveDisplay.
>
> Denis
>
>
> On Jul 28, 2011, at 4:52 AM, Howard Lewis Ship wrote:
>
>> On Wed, Jul 27, 2011 at 7:47 PM, Taha Hafeez <ta...@gmail.com> wrote:
>>> Hi Howard
>>>
>>> The lesson is, don't submit a patch for Howard's jira he will always
>>> come up with a better implementation :)
>>
>> That's not exactly the best lesson!
>>
>>>
>>> regards
>>> Taha
>>>
>>> On Thu, Jul 28, 2011 at 8:10 AM, Howard Lewis Ship <hl...@gmail.com> wrote:
>>>> On Wed, Jul 27, 2011 at 4:26 PM, Taha Hafeez <ta...@gmail.com> wrote:
>>>>> Nice !!
>>>>>
>>>>> I learned my lesson :)
>>>>>
>>>>
>>>> What lesson would that be? I just had a slightly different vision of
>>>> how this would fit in overall and how it would be implemented. The
>>>> only concrete advantage is that on a zone update you can still return
>>>> the content for the (implicit) zone to be updated along with updates
>>>> to other zones explicitly.
>>>>
>>>>> regards
>>>>> Taha
>>>>>
>>>>> On Thu, Jul 28, 2011 at 1:16 AM, Howard M. Lewis Ship (JIRA)
>>>>> <ji...@apache.org> wrote:
>>>>>>
>>>>>> [ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071942#comment-13071942 ]
>>>>>>
>>>>>> Howard M. Lewis Ship commented on TAP5-1476:
>>>>>> --------------------------------------------
>>>>>>
>>>>>> Sorry I didn't use your patch, but I think you'll like the end result.
>>>>>>
>>>>>>> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
>>>>>>> -------------------------------------------------------------------------------------
>>>>>>>
>>>>>>> Key: TAP5-1476
>>>>>>> URL: https://issues.apache.org/jira/browse/TAP5-1476
>>>>>>> Project: Tapestry 5
>>>>>>> Issue Type: Improvement
>>>>>>> Components: tapestry-core
>>>>>>> Affects Versions: 5.3
>>>>>>> Reporter: Howard M. Lewis Ship
>>>>>>> Assignee: Howard M. Lewis Ship
>>>>>>> Fix For: 5.3
>>>>>>>
>>>>>>> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>>>>>>>
>>>>>>>
>>>>>>> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
>>>>>>> I'd like to see something like:
>>>>>>> @Inject
>>>>>>> private ZoneUpdater zoneUpdater();
>>>>>>> Object onSuccess()
>>>>>>> {
>>>>>>> zoneUpdater.update("foo", fooBlock);
>>>>>>> zoneUpdater.update("bar", barBlock);
>>>>>>> return myZone.getBody();
>>>>>>> }
>>>>>>> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
>>>>>>> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
>>>>>>
>>>>>> --
>>>>>> This message is automatically generated by JIRA.
>>>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Howard M. Lewis Ship
>>>>
>>>> Creator of Apache Tapestry
>>>>
>>>> The source for Tapestry training, mentoring and support. Contact me to
>>>> learn how I can get you up and productive in Tapestry fast!
>>>>
>>>> (971) 678-5210
>>>> http://howardlewisship.com
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
Posted by Denis Stepanov <de...@gmail.com>.
Hi,
It would be nice if there was a way how to trigger a multi zone update on the client side, waiting for all zone updates to render in one request could take too long and sometimes it's better to display refreshing zones to the user.
Our simple implementation returns JS code which then triggers zone updates, because of that it would be nice to have a default event from the Zone component to refresh its content, also there could be a "pregressive" parameter which will load it's content after render and it will eleminate the need for the PregressiveDisplay.
Denis
On Jul 28, 2011, at 4:52 AM, Howard Lewis Ship wrote:
> On Wed, Jul 27, 2011 at 7:47 PM, Taha Hafeez <ta...@gmail.com> wrote:
>> Hi Howard
>>
>> The lesson is, don't submit a patch for Howard's jira he will always
>> come up with a better implementation :)
>
> That's not exactly the best lesson!
>
>>
>> regards
>> Taha
>>
>> On Thu, Jul 28, 2011 at 8:10 AM, Howard Lewis Ship <hl...@gmail.com> wrote:
>>> On Wed, Jul 27, 2011 at 4:26 PM, Taha Hafeez <ta...@gmail.com> wrote:
>>>> Nice !!
>>>>
>>>> I learned my lesson :)
>>>>
>>>
>>> What lesson would that be? I just had a slightly different vision of
>>> how this would fit in overall and how it would be implemented. The
>>> only concrete advantage is that on a zone update you can still return
>>> the content for the (implicit) zone to be updated along with updates
>>> to other zones explicitly.
>>>
>>>> regards
>>>> Taha
>>>>
>>>> On Thu, Jul 28, 2011 at 1:16 AM, Howard M. Lewis Ship (JIRA)
>>>> <ji...@apache.org> wrote:
>>>>>
>>>>> [ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071942#comment-13071942 ]
>>>>>
>>>>> Howard M. Lewis Ship commented on TAP5-1476:
>>>>> --------------------------------------------
>>>>>
>>>>> Sorry I didn't use your patch, but I think you'll like the end result.
>>>>>
>>>>>> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
>>>>>> -------------------------------------------------------------------------------------
>>>>>>
>>>>>> Key: TAP5-1476
>>>>>> URL: https://issues.apache.org/jira/browse/TAP5-1476
>>>>>> Project: Tapestry 5
>>>>>> Issue Type: Improvement
>>>>>> Components: tapestry-core
>>>>>> Affects Versions: 5.3
>>>>>> Reporter: Howard M. Lewis Ship
>>>>>> Assignee: Howard M. Lewis Ship
>>>>>> Fix For: 5.3
>>>>>>
>>>>>> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>>>>>>
>>>>>>
>>>>>> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
>>>>>> I'd like to see something like:
>>>>>> @Inject
>>>>>> private ZoneUpdater zoneUpdater();
>>>>>> Object onSuccess()
>>>>>> {
>>>>>> zoneUpdater.update("foo", fooBlock);
>>>>>> zoneUpdater.update("bar", barBlock);
>>>>>> return myZone.getBody();
>>>>>> }
>>>>>> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
>>>>>> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
>>>>>
>>>>> --
>>>>> This message is automatically generated by JIRA.
>>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>>>
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Howard M. Lewis Ship
>>>
>>> Creator of Apache Tapestry
>>>
>>> The source for Tapestry training, mentoring and support. Contact me to
>>> learn how I can get you up and productive in Tapestry fast!
>>>
>>> (971) 678-5210
>>> http://howardlewisship.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by Howard Lewis Ship <hl...@gmail.com>.
On Wed, Jul 27, 2011 at 7:47 PM, Taha Hafeez <ta...@gmail.com> wrote:
> Hi Howard
>
> The lesson is, don't submit a patch for Howard's jira he will always
> come up with a better implementation :)
That's not exactly the best lesson!
>
> regards
> Taha
>
> On Thu, Jul 28, 2011 at 8:10 AM, Howard Lewis Ship <hl...@gmail.com> wrote:
>> On Wed, Jul 27, 2011 at 4:26 PM, Taha Hafeez <ta...@gmail.com> wrote:
>>> Nice !!
>>>
>>> I learned my lesson :)
>>>
>>
>> What lesson would that be? I just had a slightly different vision of
>> how this would fit in overall and how it would be implemented. The
>> only concrete advantage is that on a zone update you can still return
>> the content for the (implicit) zone to be updated along with updates
>> to other zones explicitly.
>>
>>> regards
>>> Taha
>>>
>>> On Thu, Jul 28, 2011 at 1:16 AM, Howard M. Lewis Ship (JIRA)
>>> <ji...@apache.org> wrote:
>>>>
>>>> [ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071942#comment-13071942 ]
>>>>
>>>> Howard M. Lewis Ship commented on TAP5-1476:
>>>> --------------------------------------------
>>>>
>>>> Sorry I didn't use your patch, but I think you'll like the end result.
>>>>
>>>>> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
>>>>> -------------------------------------------------------------------------------------
>>>>>
>>>>> Key: TAP5-1476
>>>>> URL: https://issues.apache.org/jira/browse/TAP5-1476
>>>>> Project: Tapestry 5
>>>>> Issue Type: Improvement
>>>>> Components: tapestry-core
>>>>> Affects Versions: 5.3
>>>>> Reporter: Howard M. Lewis Ship
>>>>> Assignee: Howard M. Lewis Ship
>>>>> Fix For: 5.3
>>>>>
>>>>> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>>>>>
>>>>>
>>>>> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
>>>>> I'd like to see something like:
>>>>> @Inject
>>>>> private ZoneUpdater zoneUpdater();
>>>>> Object onSuccess()
>>>>> {
>>>>> zoneUpdater.update("foo", fooBlock);
>>>>> zoneUpdater.update("bar", barBlock);
>>>>> return myZone.getBody();
>>>>> }
>>>>> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
>>>>> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
>>>>
>>>> --
>>>> This message is automatically generated by JIRA.
>>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>>
>>
>> --
>> Howard M. Lewis Ship
>>
>> Creator of Apache Tapestry
>>
>> The source for Tapestry training, mentoring and support. Contact me to
>> learn how I can get you up and productive in Tapestry fast!
>>
>> (971) 678-5210
>> http://howardlewisship.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by Taha Hafeez <ta...@gmail.com>.
Hi Howard
The lesson is, don't submit a patch for Howard's jira he will always
come up with a better implementation :)
regards
Taha
On Thu, Jul 28, 2011 at 8:10 AM, Howard Lewis Ship <hl...@gmail.com> wrote:
> On Wed, Jul 27, 2011 at 4:26 PM, Taha Hafeez <ta...@gmail.com> wrote:
>> Nice !!
>>
>> I learned my lesson :)
>>
>
> What lesson would that be? I just had a slightly different vision of
> how this would fit in overall and how it would be implemented. The
> only concrete advantage is that on a zone update you can still return
> the content for the (implicit) zone to be updated along with updates
> to other zones explicitly.
>
>> regards
>> Taha
>>
>> On Thu, Jul 28, 2011 at 1:16 AM, Howard M. Lewis Ship (JIRA)
>> <ji...@apache.org> wrote:
>>>
>>> [ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071942#comment-13071942 ]
>>>
>>> Howard M. Lewis Ship commented on TAP5-1476:
>>> --------------------------------------------
>>>
>>> Sorry I didn't use your patch, but I think you'll like the end result.
>>>
>>>> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
>>>> -------------------------------------------------------------------------------------
>>>>
>>>> Key: TAP5-1476
>>>> URL: https://issues.apache.org/jira/browse/TAP5-1476
>>>> Project: Tapestry 5
>>>> Issue Type: Improvement
>>>> Components: tapestry-core
>>>> Affects Versions: 5.3
>>>> Reporter: Howard M. Lewis Ship
>>>> Assignee: Howard M. Lewis Ship
>>>> Fix For: 5.3
>>>>
>>>> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>>>>
>>>>
>>>> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
>>>> I'd like to see something like:
>>>> @Inject
>>>> private ZoneUpdater zoneUpdater();
>>>> Object onSuccess()
>>>> {
>>>> zoneUpdater.update("foo", fooBlock);
>>>> zoneUpdater.update("bar", barBlock);
>>>> return myZone.getBody();
>>>> }
>>>> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
>>>> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by Howard Lewis Ship <hl...@gmail.com>.
On Wed, Jul 27, 2011 at 4:26 PM, Taha Hafeez <ta...@gmail.com> wrote:
> Nice !!
>
> I learned my lesson :)
>
What lesson would that be? I just had a slightly different vision of
how this would fit in overall and how it would be implemented. The
only concrete advantage is that on a zone update you can still return
the content for the (implicit) zone to be updated along with updates
to other zones explicitly.
> regards
> Taha
>
> On Thu, Jul 28, 2011 at 1:16 AM, Howard M. Lewis Ship (JIRA)
> <ji...@apache.org> wrote:
>>
>> [ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071942#comment-13071942 ]
>>
>> Howard M. Lewis Ship commented on TAP5-1476:
>> --------------------------------------------
>>
>> Sorry I didn't use your patch, but I think you'll like the end result.
>>
>>> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
>>> -------------------------------------------------------------------------------------
>>>
>>> Key: TAP5-1476
>>> URL: https://issues.apache.org/jira/browse/TAP5-1476
>>> Project: Tapestry 5
>>> Issue Type: Improvement
>>> Components: tapestry-core
>>> Affects Versions: 5.3
>>> Reporter: Howard M. Lewis Ship
>>> Assignee: Howard M. Lewis Ship
>>> Fix For: 5.3
>>>
>>> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>>>
>>>
>>> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
>>> I'd like to see something like:
>>> @Inject
>>> private ZoneUpdater zoneUpdater();
>>> Object onSuccess()
>>> {
>>> zoneUpdater.update("foo", fooBlock);
>>> zoneUpdater.update("bar", barBlock);
>>> return myZone.getBody();
>>> }
>>> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
>>> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
>>
>> --
>> This message is automatically generated by JIRA.
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by Taha Hafeez <ta...@gmail.com>.
Nice !!
I learned my lesson :)
regards
Taha
On Thu, Jul 28, 2011 at 1:16 AM, Howard M. Lewis Ship (JIRA)
<ji...@apache.org> wrote:
>
> [ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071942#comment-13071942 ]
>
> Howard M. Lewis Ship commented on TAP5-1476:
> --------------------------------------------
>
> Sorry I didn't use your patch, but I think you'll like the end result.
>
>> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
>> -------------------------------------------------------------------------------------
>>
>> Key: TAP5-1476
>> URL: https://issues.apache.org/jira/browse/TAP5-1476
>> Project: Tapestry 5
>> Issue Type: Improvement
>> Components: tapestry-core
>> Affects Versions: 5.3
>> Reporter: Howard M. Lewis Ship
>> Assignee: Howard M. Lewis Ship
>> Fix For: 5.3
>>
>> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>>
>>
>> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
>> I'd like to see something like:
>> @Inject
>> private ZoneUpdater zoneUpdater();
>> Object onSuccess()
>> {
>> zoneUpdater.update("foo", fooBlock);
>> zoneUpdater.update("bar", barBlock);
>> return myZone.getBody();
>> }
>> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
>> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: [jira] [Updated] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "dragan.sahpaskix@gmail.com" <dr...@gmail.com>.
Hi,
On Wed, Jul 6, 2011 at 10:16 AM, Taha Hafeez <ta...@gmail.com>wrote:
> Hi Dragan,
>
> On Wed, Jul 6, 2011 at 1:21 PM, dragan.sahpaskix@gmail.com <
> dragan.sahpaskix@gmail.com> wrote:
>
> > Hi Taha,
> > I was looking at the new tests and didn't figure out how to update
> multiple
> > zones but not the zone triggering the ajax.
> >
> > This corresponds to the scenario when you return a MultiZoneUpdate not
> > containig the zone triggering the ajax. I have used this many many times
> > when a component renders a dummy zone and a containing page or, component
> > provides the multiZoneUpdate as a result to a custom event that in the
> end
> > does not contain the zone triggering the update.
> >
> >
> I have not come across such a scenario so I didn't include it. A way to
> take
> care of this case that I can think of is returning the ZoneUpdater instance
> which can be handled in the same way MultiZoneUpdate is. (Actually I just
> used the code from MultiZoneUpdateEventResultProcessor in
> ZoneUpdaterProcessorImpl)
> What do you say ?
OK, that's great I wasn't aware because it was not in the test cases.
>
>
>
> > Also, I didn't saw tests for ZoneUpdater.add(String zoneId, Object
> > renderer) or have I missed something.
> >
> > add(ClientBodyElement) calls add(String,Object) internally so I didn't
> include it. Yes, can add a test for blocks which will include that method
> too.
>
Awsome.
Cheers,
Dragan Sahpaski
>
>
> > Cheers,
> > Dragan Sahpaski
> >
> >
> Thanks for evaluating/analyzing
>
> regards
> Taha
>
>
> >
> >
> > On Wed, Jul 6, 2011 at 9:26 AM, Taha Hafeez (JIRA) <ji...@apache.org>
> > wrote:
> >
> > >
> > > [
> > >
> >
> https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> > ]
> > >
> > > Taha Hafeez updated TAP5-1476:
> > > ------------------------------
> > >
> > > Attachment: zone-updater.patch
> > >
> > > Patch which injects a ZoneUpdater into the Environment. The processing
> is
> > > done by ZoneUpdaterProcessor. Does a modification to
> > > AjaxComponentEventRequestHandler.java
> > >
> > > > Deprecate MultiZoneUpdate, replace with an injectable service to
> > collect
> > > zone updates
> > > >
> > >
> >
> -------------------------------------------------------------------------------------
> > > >
> > > > Key: TAP5-1476
> > > > URL: https://issues.apache.org/jira/browse/TAP5-1476
> > > > Project: Tapestry 5
> > > > Issue Type: Improvement
> > > > Components: tapestry-core
> > > > Affects Versions: 5.3
> > > > Reporter: Howard M. Lewis Ship
> > > > Attachments: zone-updater.patch
> > > >
> > > >
> > > > MultiZoneUpdate presumes that there's a single place where all the
> zone
> > > to be updated are known. This is not necessarilly the case.
> > > > I'd like to see something like:
> > > > @Inject
> > > > private ZoneUpdater zoneUpdater();
> > > > Object onSuccess()
> > > > {
> > > > zoneUpdater.update("foo", fooBlock);
> > > > zoneUpdater.update("bar", barBlock);
> > > > return myZone.getBody();
> > > > }
> > > > The main point here is that different event handlers would all be
> able
> > to
> > > invoke ZoneUpdater.update() .
> > > > This would also allow a single response to render main content (for
> the
> > > requesting Zone on the client) plus zone updates to named zones.
> > >
> > > --
> > > This message is automatically generated by JIRA.
> > > For more information on JIRA, see:
> > http://www.atlassian.com/software/jira
> > >
> > >
> > >
> >
>
Re: [jira] [Updated] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by Taha Hafeez <ta...@gmail.com>.
Hi Dragan,
On Wed, Jul 6, 2011 at 1:21 PM, dragan.sahpaskix@gmail.com <
dragan.sahpaskix@gmail.com> wrote:
> Hi Taha,
> I was looking at the new tests and didn't figure out how to update multiple
> zones but not the zone triggering the ajax.
>
> This corresponds to the scenario when you return a MultiZoneUpdate not
> containig the zone triggering the ajax. I have used this many many times
> when a component renders a dummy zone and a containing page or, component
> provides the multiZoneUpdate as a result to a custom event that in the end
> does not contain the zone triggering the update.
>
>
I have not come across such a scenario so I didn't include it. A way to take
care of this case that I can think of is returning the ZoneUpdater instance
which can be handled in the same way MultiZoneUpdate is. (Actually I just
used the code from MultiZoneUpdateEventResultProcessor in
ZoneUpdaterProcessorImpl)
What do you say ?
> Also, I didn't saw tests for ZoneUpdater.add(String zoneId, Object
> renderer) or have I missed something.
>
> add(ClientBodyElement) calls add(String,Object) internally so I didn't
include it. Yes, can add a test for blocks which will include that method
too.
> Cheers,
> Dragan Sahpaski
>
>
Thanks for evaluating/analyzing
regards
Taha
>
>
> On Wed, Jul 6, 2011 at 9:26 AM, Taha Hafeez (JIRA) <ji...@apache.org>
> wrote:
>
> >
> > [
> >
> https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
> >
> > Taha Hafeez updated TAP5-1476:
> > ------------------------------
> >
> > Attachment: zone-updater.patch
> >
> > Patch which injects a ZoneUpdater into the Environment. The processing is
> > done by ZoneUpdaterProcessor. Does a modification to
> > AjaxComponentEventRequestHandler.java
> >
> > > Deprecate MultiZoneUpdate, replace with an injectable service to
> collect
> > zone updates
> > >
> >
> -------------------------------------------------------------------------------------
> > >
> > > Key: TAP5-1476
> > > URL: https://issues.apache.org/jira/browse/TAP5-1476
> > > Project: Tapestry 5
> > > Issue Type: Improvement
> > > Components: tapestry-core
> > > Affects Versions: 5.3
> > > Reporter: Howard M. Lewis Ship
> > > Attachments: zone-updater.patch
> > >
> > >
> > > MultiZoneUpdate presumes that there's a single place where all the zone
> > to be updated are known. This is not necessarilly the case.
> > > I'd like to see something like:
> > > @Inject
> > > private ZoneUpdater zoneUpdater();
> > > Object onSuccess()
> > > {
> > > zoneUpdater.update("foo", fooBlock);
> > > zoneUpdater.update("bar", barBlock);
> > > return myZone.getBody();
> > > }
> > > The main point here is that different event handlers would all be able
> to
> > invoke ZoneUpdater.update() .
> > > This would also allow a single response to render main content (for the
> > requesting Zone on the client) plus zone updates to named zones.
> >
> > --
> > This message is automatically generated by JIRA.
> > For more information on JIRA, see:
> http://www.atlassian.com/software/jira
> >
> >
> >
>
Re: [jira] [Updated] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "dragan.sahpaskix@gmail.com" <dr...@gmail.com>.
Hi Taha,
I was looking at the new tests and didn't figure out how to update multiple
zones but not the zone triggering the ajax.
This corresponds to the scenario when you return a MultiZoneUpdate not
containig the zone triggering the ajax. I have used this many many times
when a component renders a dummy zone and a containing page or, component
provides the multiZoneUpdate as a result to a custom event that in the end
does not contain the zone triggering the update.
Also, I didn't saw tests for ZoneUpdater.add(String zoneId, Object
renderer) or have I missed something.
Cheers,
Dragan Sahpaski
On Wed, Jul 6, 2011 at 9:26 AM, Taha Hafeez (JIRA) <ji...@apache.org> wrote:
>
> [
> https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Taha Hafeez updated TAP5-1476:
> ------------------------------
>
> Attachment: zone-updater.patch
>
> Patch which injects a ZoneUpdater into the Environment. The processing is
> done by ZoneUpdaterProcessor. Does a modification to
> AjaxComponentEventRequestHandler.java
>
> > Deprecate MultiZoneUpdate, replace with an injectable service to collect
> zone updates
> >
> -------------------------------------------------------------------------------------
> >
> > Key: TAP5-1476
> > URL: https://issues.apache.org/jira/browse/TAP5-1476
> > Project: Tapestry 5
> > Issue Type: Improvement
> > Components: tapestry-core
> > Affects Versions: 5.3
> > Reporter: Howard M. Lewis Ship
> > Attachments: zone-updater.patch
> >
> >
> > MultiZoneUpdate presumes that there's a single place where all the zone
> to be updated are known. This is not necessarilly the case.
> > I'd like to see something like:
> > @Inject
> > private ZoneUpdater zoneUpdater();
> > Object onSuccess()
> > {
> > zoneUpdater.update("foo", fooBlock);
> > zoneUpdater.update("bar", barBlock);
> > return myZone.getBody();
> > }
> > The main point here is that different event handlers would all be able to
> invoke ZoneUpdater.update() .
> > This would also allow a single response to render main content (for the
> requesting Zone on the client) plus zone updates to named zones.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
[jira] [Closed] (TAP5-1476) Deprecate MultiZoneUpdate, replace with
an injectable service to collect zone updates
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1476.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Taha Hafeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taha Hafeez updated TAP5-1476:
------------------------------
Attachment: zone_updater_with_zone-updater_as_return.patch
Granted license
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Taha Hafeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taha Hafeez updated TAP5-1476:
------------------------------
Attachment: zone-updater.patch
Patch which injects a ZoneUpdater into the Environment. The processing is done by ZoneUpdaterProcessor. Does a modification to AjaxComponentEventRequestHandler.java
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Attachments: zone-updater.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TAP5-1476) Deprecate MultiZoneUpdate, replace with
an injectable service to collect zone updates
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1476.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.3
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1476:
------------------------------------------
Assignee: Howard M. Lewis Ship
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071977#comment-13071977 ]
Hudson commented on TAP5-1476:
------------------------------
Integrated in tapestry-trunk-freestyle #437 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/437/])
TAP5-1476: Rename methods on AjaxResponseRenderer
Add a test for AjaxResponseRenderer.addCallback()
Fix a bug in AjaxResponseRenderer.addCallback() where the filter did not invoke the next renderer, which prevent most of the content from being constructed
TAP5-1476: Update the demo page for MultiZoneUpdate to use the new AjaxResponseRenderer API as well
TAP5-1476: Work out implementation of AjaxResponseRenderer and re-implement MultiZoneUpdateEventResultProcessor to mostly work by invoking AjaxResponseRenderer methods
TAP5-1476: Move SingleZonePartialRendererFilter to an internal package
TAP5-1476: Mark MultiZoneUpdate as deprecated
TAP5-1476: Mark MultiZoneUpdateEventResultProcessor as deprecated, and move it to a more appropriate internal package
TAP5-1476: Start of work on AjaxResponseRenderer
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151571
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/MultiZoneUpdateDemo.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/AjaxResponseRendererImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/ZoneTests.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/integration/app1/pages/MultiZoneUpdateDemo.js
* /tapestry/tapestry5/trunk/tapestry-core/src/test/app1/MultiZoneUpdateDemo.tml
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/AjaxResponseRenderer.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/JavaScriptCallback.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151570
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/MultiZoneUpdateDemo.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151569
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/AjaxResponseRendererImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/SingleZonePartialRendererFilter.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/AjaxResponseRenderer.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/JavaScriptCallback.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/SetupZonesFilter.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151567
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/SingleZonePartialRendererFilter.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/SetupZonesFilter.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/SingleZonePartialRendererFilter.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151566
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/AjaxResponseRenderer.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/ajax/MultiZoneUpdate.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151565
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/PageRenderQueue.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151564
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/AjaxResponseRenderer.java
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071942#comment-13071942 ]
Howard M. Lewis Ship commented on TAP5-1476:
--------------------------------------------
Sorry I didn't use your patch, but I think you'll like the end result.
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Taha Hafeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taha Hafeez updated TAP5-1476:
------------------------------
Attachment: zone_updater_with_zone-updater_as_return.patch
Added AjaxUpdaterEventRequestProcessor for handling ZoneUpdater as return value from ajax request. Please see http://tapestry.1045711.n5.nabble.com/Re-jira-Updated-TAP5-1476-Deprecate-MultiZoneUpdate-replace-with-an-injectable-service-to-collect-zos-tp4556067p4556114.html
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1476:
------------------------------------------
Assignee: Howard M. Lewis Ship
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Taha Hafeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taha Hafeez updated TAP5-1476:
------------------------------
Attachment: zone_updater_with_zone-updater_as_return.patch
Granted license
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Tom van Dijk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007519#comment-13007519 ]
Tom van Dijk commented on TAP5-1476:
------------------------------------
Okay, what if I have an actionLink without a zone parameter and I simply want to update zones depending on server state?
And what if sometimes I just update no zones at all?
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3.0
> Reporter: Howard M. Lewis Ship
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Taha Hafeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taha Hafeez updated TAP5-1476:
------------------------------
Attachment: zone-updater.patch
Patch which injects a ZoneUpdater into the Environment. The processing is done by ZoneUpdaterProcessor. Does a modification to AjaxComponentEventRequestHandler.java
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Attachments: zone-updater.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071942#comment-13071942 ]
Howard M. Lewis Ship commented on TAP5-1476:
--------------------------------------------
Sorry I didn't use your patch, but I think you'll like the end result.
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Taha Hafeez (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taha Hafeez updated TAP5-1476:
------------------------------
Attachment: zone_updater_with_zone-updater_as_return.patch
Added AjaxUpdaterEventRequestProcessor for handling ZoneUpdater as return value from ajax request. Please see http://tapestry.1045711.n5.nabble.com/Re-jira-Updated-TAP5-1476-Deprecate-MultiZoneUpdate-replace-with-an-injectable-service-to-collect-zos-tp4556067p4556114.html
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071977#comment-13071977 ]
Hudson commented on TAP5-1476:
------------------------------
Integrated in tapestry-trunk-freestyle #437 (See [https://builds.apache.org/job/tapestry-trunk-freestyle/437/])
TAP5-1476: Rename methods on AjaxResponseRenderer
Add a test for AjaxResponseRenderer.addCallback()
Fix a bug in AjaxResponseRenderer.addCallback() where the filter did not invoke the next renderer, which prevent most of the content from being constructed
TAP5-1476: Update the demo page for MultiZoneUpdate to use the new AjaxResponseRenderer API as well
TAP5-1476: Work out implementation of AjaxResponseRenderer and re-implement MultiZoneUpdateEventResultProcessor to mostly work by invoking AjaxResponseRenderer methods
TAP5-1476: Move SingleZonePartialRendererFilter to an internal package
TAP5-1476: Mark MultiZoneUpdate as deprecated
TAP5-1476: Mark MultiZoneUpdateEventResultProcessor as deprecated, and move it to a more appropriate internal package
TAP5-1476: Start of work on AjaxResponseRenderer
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151571
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/MultiZoneUpdateDemo.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/AjaxResponseRendererImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/ZoneTests.java
* /tapestry/tapestry5/trunk/tapestry-core/src/test/resources/org/apache/tapestry5/integration/app1/pages/MultiZoneUpdateDemo.js
* /tapestry/tapestry5/trunk/tapestry-core/src/test/app1/MultiZoneUpdateDemo.tml
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/AjaxResponseRenderer.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/JavaScriptCallback.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151570
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/test/java/org/apache/tapestry5/integration/app1/pages/MultiZoneUpdateDemo.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151569
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/AjaxResponseRendererImpl.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/SingleZonePartialRendererFilter.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/AjaxResponseRenderer.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/JavaScriptCallback.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/SetupZonesFilter.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151567
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/SingleZonePartialRendererFilter.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/SetupZonesFilter.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/SingleZonePartialRendererFilter.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151566
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/AjaxResponseRenderer.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/ajax/MultiZoneUpdate.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151565
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/PageRenderQueue.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/MultiZoneUpdateEventResultProcessor.java
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1151564
Files :
* /tapestry/tapestry5/trunk/tapestry-core/src/main/java/org/apache/tapestry5/services/ajax/AjaxResponseRenderer.java
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3
>
> Attachments: zone-updater.patch, zone_updater_with_zone-updater_as_return.patch, zone_updater_with_zone-updater_as_return.patch
>
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TAP5-1476) Deprecate MultiZoneUpdate, replace
with an injectable service to collect zone updates
Posted by "Tom van Dijk (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007519#comment-13007519 ]
Tom van Dijk commented on TAP5-1476:
------------------------------------
Okay, what if I have an actionLink without a zone parameter and I simply want to update zones depending on server state?
And what if sometimes I just update no zones at all?
> Deprecate MultiZoneUpdate, replace with an injectable service to collect zone updates
> -------------------------------------------------------------------------------------
>
> Key: TAP5-1476
> URL: https://issues.apache.org/jira/browse/TAP5-1476
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.3.0
> Reporter: Howard M. Lewis Ship
>
> MultiZoneUpdate presumes that there's a single place where all the zone to be updated are known. This is not necessarilly the case.
> I'd like to see something like:
> @Inject
> private ZoneUpdater zoneUpdater();
> Object onSuccess()
> {
> zoneUpdater.update("foo", fooBlock);
> zoneUpdater.update("bar", barBlock);
> return myZone.getBody();
> }
> The main point here is that different event handlers would all be able to invoke ZoneUpdater.update() .
> This would also allow a single response to render main content (for the requesting Zone on the client) plus zone updates to named zones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira