[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [osee-dev] RE: Remote Event Service Re-Arch
- From: "Brooks, Ryan D" <ryan.d.brooks@xxxxxxxxxx>
- Date: Tue, 28 Jul 2009 12:25:51 -0700
- Delivered-to: email@example.com
- Thread-index: AcoFm3iRvYZ+4LjIQUilID8DHToKcADtk6RwAZc01MA=
- Thread-topic: [osee-dev] RE: Remote Event Service Re-Arch
Here is what I found in IPZilla for the 13 libraries used by the
publish/subscribe example Andy referred to. If we switch to using
spring 2.5.2, then the 4 spring jars listed in the first category can be
moved to the second (CQs that can be used for a piggy-back CQ) which is
less work for the Eclipse Foundation legal staff.
The following jars have an associated CQ that provides precedence for an
earlier version that was approved:
spring-aop-2.5.6.jar CQ#: 2325 "spring-aop Version: 2.5.2"
spring-core-2.5.6.jar CQ#: 2329 "spring-core Version: 2.5.2"
spring-beans-2.5.6.jar CQ#: 2326 "spring-beans Version: 2.5.2"
spring-context-2.5.6.jar CQ#: 2328 "spring-context Version: 2.5.2"
camel-jms-2.0-M2.jar CQ#: 2706 "Apache ActiveMQ Camel JMS Version:
camel-core-2.0-M2.jar CQ#: 2704 "Apache ActiveMQ Camel Core
camel-spring-2.0-M2.jar CQ#: 2707 "Apache ActiveMQ Camel Spring
The following jars have an associated CQ that can be used for a
activemq-core-5.2.0.jar CQ#: 2580 "ActiveMQ Version: 5.2 (Subset)"
activemq-camel-5.2.0.jar CQ#: 2580 "ActiveMQ Version: 5.2 (Subset)"
"geronimo-j2ee-management_1.0_spec-1.0 Version: 1.0."
There were CQs for the following, but they were withdrawn:
From: Finkbeiner, Andrew M
Sent: Monday, July 20, 2009 9:11 AM
Subject: [osee-dev] RE: Remote Event Service Re-Arch
I was able to get a simple publish subscribe example working using camel
and activemq. I think the test at least demonstrates that camel and
activemq are useful technologies that we can build on without much
There were 13 libraries used:
If anyone wants to look at the simple project I created let me know and
I'll get you the source.
> From: Finkbeiner, Andrew M
> Sent: Wednesday, July 15, 2009 3:28 PM
> To: 'osee-dev@xxxxxxxxxxx'
> Subject: Remote Event Service Re-Arch
> Because of various Jini and architecture problems with the current
> implementation of our event service we are working towards a new
> implementation for the next OSEE release.
> Both ActiveMQ http://activemq.apache.org/ and Camel
> http://camel.apache.org/ have been talked about as possible building
> blocks for the new architecture. Are there other libraries we should
> consider? Let's try to come up with a strategy for the re-arch and
> maybe start a list of known use-case issues that we want to be sure we
> have handled. Thoughts?
osee-dev mailing list