Yes that's correct. That's one of the reasons why I have become less of a fan around observer/listener semantics of any type lately and more towards message-based communication for tree events/property changes, etc.
Anyway, that's fine. The annotation base class that I'll offer up as the starting point allows the listener class to be specified so it can be implemented as a subclass of the base listener class that is automatically created to support annotations like this. The default can be a strong subscription. At the same time, I'll mention that the default can be set to strong so it takes a conscious choice to make it weak and there are a lot of good weak use cases where having this would be nice. In this case, its all about convenience. -----Original Message----- From: Noel Grandin (JIRA) [mailto:j...@apache.org] Sent: Sunday, June 20, 2010 5:00 AM To: dev@pivot.apache.org Subject: [jira] Commented: (PIVOT-535) Add a @MessageListener annotation and an annotation processor for application context message listener [ https://issues.apache.org/jira/browse/PIVOT-535?page=com.atlassian.jira.plug in.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880607#action_1 2880607 ] Noel Grandin commented on PIVOT-535: ------------------------------------ See (some parts of) the earlier discussion we had about weak listeners here: http://www.mail-archive.com/pivot-...@incubator.apache.org/msg03847.html Bottom line is that weak listeners are a bad idea. > Add a @MessageListener annotation and an annotation processor for application context message listener > ---------------------------------------------------------------------------- -------------------------- > > Key: PIVOT-535 > URL: https://issues.apache.org/jira/browse/PIVOT-535 > Project: Pivot > Issue Type: Improvement > Reporter: Appddevvv > > Add a message listener annotation and a static method for annotation processing to automatically enroll instance/methods in application message handling. > I have the classes that I can submit as a starting point. They allow weak and strong references as well as optional request-reply semantics. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
