[
https://issues.apache.org/jira/browse/TAP5-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121181#comment-14121181
]
Dmitry Gusev commented on TAP5-2383:
------------------------------------
[~uklance]
bq. I don't think so, I think these are different types of events. In my
example I used a new annotation @Subscribe("personUpdated"). You could have one
call the other if you wish.
Say you have a page:
{code}
class MyPage {
@Subscribe("event1")
void onMyEvent() {
// handle
}
}
{code}
You can have {{<t:eventLink t:id="myEvent">...}} that will trigger the same
event handler. Now, how this event will be handled, using bubbling or
publishing?
Or are you suggesting to implement {{<t:publishLink t:id="myEvent">...}} to
define the behavior?
{quote}
Did you see my code?
{code}componentResources.publish("personUpdated", person); // new method on
ComponentResources{code}
As I said, publishing is a service invocation. Invoke it when and where you
need.
{quote}
Yes, I saw that. I was just saying that it doesn't feel right to have
{{publish}} method on ComponentResources, because it only knows about
parent/child component relations of specific page relative to current component.
> 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)
