I have implemented something like this in the past. The problem is that you likely want your Events to travel over many different protocols like JMS, JXTA, Jgroups etc. One solution is to have an EventPublisher service that clients can retrieve from the context by some attribute. The standard Event classes can be reused. The result is a per-component abstraction that isolates clients both from the specific topic they are publishing to and from the protocol they are using.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andrea Zoppello Sent: 2009, May, 20 3:56 AM To: OSGi - Dev Subject: [osgi-dev] EventAdmin on JMS??? Hi All, Event Admin service is in my opinion one of the most useful OSGi service of the compendium and after studying and playing with it, i found out that some concepts are *common* or similar to JMS. So i've start to think if *could make sense* to have an Event Admin implementation based on JMS, this could have some great benefits for example, event could be persisted and we will benefit from the features offered by jms brokers... I'm just writing here to discuss about this with the community. Does this idea make sense??? Is that someone that had already the same idea??? Are there some just implementation of this??? Andrea Zoppello _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev ________________________________________ This E-Mail (including any attachments) may contain privileged or confidential information. It is intended only for the addressee(s) indicated above. The sender does not waive any of its rights, privileges or other protections respecting this information. Any distribution, copying or other use of this E-Mail or the information it contains, by other than an intended recipient, is not sanctioned and is prohibited. If you received this E-Mail in error, please delete it and advise the sender (by return E-Mail or otherwise) immediately. This E-Mail (including any attachments) has been scanned for viruses. It is believed to be free of any virus or other defect that might affect any computer system into which it is received and opened. However, it is the responsibility of the recipient to ensure that it is virus free. The sender accepts no responsibility for any loss or damage arising in any way from its use. E-Mail received by or sent from RBC Capital Markets is subject to review by Supervisory personnel. Such communications are retained and may be produced to regulatory authorities or others with legal rights to the information. IRS CIRCULAR 230 NOTICE: TO COMPLY WITH U.S. TREASURY REGULATIONS, WE ADVISE YOU THAT ANY U.S. FEDERAL TAX ADVISE INCLUDED IN THIS COMMUNICATION IS NOT INTENDED OR WRITTEN TO BE USED, AND CANNOT BE USED, TO AVOID ANY U.S. FEDERAL TAX PENALTIES OR TO PROMOTE, MARKET, OR RECOMMEND TO ANOTHER PARTY ANY TRANSACTION OR MATTER. _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
