[
https://issues.apache.org/jira/browse/TAP5-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124728#comment-14124728
]
Geoff Callender edited comment on TAP5-2383 at 9/7/14 12:59 AM:
----------------------------------------------------------------
[~uklance]
Take your example a step further - what if the messages list has a filter? Only
the client will know the filter value, and therefore only the client will know
the current messages list.
You can see this exact problem being handled, clumsily, server-side, in
PersonList.doChangeOfSelectedPerson() in
http://jumpstart.doublenegative.com.au/jumpstart7/together/ajaxcomponentscrud/persons
. That method is called by its container, Persons, in response to various
events elsewhere on the page. You can see it's just plain messy and brittle.
was (Author: geoffcallender):
[~uklance]
Take your example a step further - what if the messages list has a filter? Only
the client will know the filter value, and therefore only the client will know
the current messages list.
You can see this exact problem being handled, clumsily, server-side, in
PersonList.doChangeOfSelectedPerson() in
http://jumpstart.doublenegative.com.au/jumpstart7/together/ajaxcomponentscrud/persons
. PersonList.doChangeOfSelectedPerson() is called by its container, Persons,
in response to various events elsewhere on the page. You can see it's just
plain messy and brittle.
> Serverside publish / subscribe mechanism
> ----------------------------------------
>
> Key: TAP5-2383
> URL: https://issues.apache.org/jira/browse/TAP5-2383
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Lance
> Priority: Minor
>
> In some cases, an event in one component should cause an action (eg ajax
> update) in another. When these components are siblings it sometimes gets
> tricky having to pass zone id's around and having one component update the
> other.
> It would be nice to decouple the components with a serverside pub/sub
> mechanism. Here's an initial brain dump on how it could work.
> {code:java}
> public class EditPersonComponent {
> @Parameter
> private Person person;
> @Inject
> private PersonDao personDao;
> @Inject
> private ComponentResources componentResources;
> // lets assume there's a form in the component which gets posted
> void onSuccessFromPersonForm() {
> personDao.save(person);
> componentResources.publish("personUpdated", person); // new method on
> ComponentResources
> }
> }
> {code}
> {code:java}
> public class SomeOtherComponent {
> @Inject
> private AjaxResponseRenderer ajaxResponseRenderer;
> @Property
> private Person person;
> @Inject
> private Zone personZone;
> // new subscribe annotation (and naming convention?)
> @Subscribe("personUpdated")
> void onPersonUpdatedPublished(Person person) {
> this.person = person;
> ajaxResponseRenderer.addRender(personZone);
> }
> }
> {code}
> If this change was made on ComponentResources, we should probably add the
> following to support invoking publish events on the client
> {code}
> Link ComponentResources.createPublishLink(String eventType, Object... context)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
