[
https://issues.apache.org/jira/browse/TAP5-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121215#comment-14121215
]
Lance edited comment on TAP5-2383 at 9/4/14 10:26 AM:
------------------------------------------------------
{quote}Like I was saying before – I don't feel we need another (second) kind of
event types, because there's no really benefits.{quote}
Normal event handlers will often return block. This feels a bit wrong for a
subscription handler which should return void. I guess we could re-use them.
{quote}This won't work if publisher and subscriber are on different pages, like
when your trigger component is from a block that is from one page, and your
subscribers are from active page that's just rendered the source component via
{{<t:deletage ... />}}{quote}
I finally get you. Whilst logically these components are on the same web page,
they are actually on different pages on the serverside. I'd have to have a
think about this case.
I finally see why you think ComponentResources is possibly not the best place!
was (Author: uklance):
{quote}Like I was saying before – I don't feel we need another (second) kind of
event types, because there's no really benefits.{quote}
Normal event handlers will often return block. This feels a bit wrong for a
subscription handler which should return void. I guess we could re-use them.
{quote}This won't work if publisher and subscriber are on different pages, like
when your trigger component is from a block that is from one page, and your
subscribers are from active page that's just rendered the source component via
{{<t:deletage ... />}}{quote}
I finally get you. Whilst logically these components are on the same web page,
they are actually on different pages on the serverside. I'd have to have a
think about this case.
> 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)
