[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [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:
1.4.0"
camel-core-2.0-M2.jar      CQ#: 2704 "Apache ActiveMQ Camel Core
Version: 1.4.0"
camel-spring-2.0-M2.jar    CQ#: 2707 "Apache ActiveMQ Camel Spring
Version: 1.4.0"

The following jars have an associated CQ that can be used for a
piggy-back CQ:
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.jar   CQ#2708
"geronimo-j2ee-management_1.0_spec-1.0 Version: 1.0."

There were CQs for the following, but they were withdrawn:
spring-jms-2.5.5.jar
spring-tx-2.5.5.jar
geronimo-jms_1.1_spec-1.1.1.jar

Regards,
Ryan Brooks

-----Original Message-----
From: Finkbeiner, Andrew M 
Sent: Monday, July 20, 2009 9:11 AM
To: osee-dev@xxxxxxxxxxx
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
technical difficulty.  

There were 13 libraries used:

/test.activemq.pub.sub/libs/spring-aop-2.5.6.jar
/test.activemq.pub.sub/libs/spring-core-2.5.6.jar
/test.activemq.pub.sub/libs/spring-beans-2.5.6.jar
/test.activemq.pub.sub/libs/spring-jms-2.5.5.jar
/test.activemq.pub.sub/libs/spring-tx-2.5.5.jar
/test.activemq.pub.sub/libs/spring-context-2.5.6.jar
/test.activemq.pub.sub/libs/camel-jms-2.0-M2.jar
/test.activemq.pub.sub/libs/activemq-core-5.2.0.jar
/test.activemq.pub.sub/libs/geronimo-j2ee-management_1.0_spec-1.0.jar
/test.activemq.pub.sub/libs/geronimo-jms_1.1_spec-1.1.1.jar
/test.activemq.pub.sub/libs/camel-spring-2.0-M2.jar
/test.activemq.pub.sub/libs/activemq-camel-5.2.0.jar
/test.activemq.pub.sub/libs/camel-core-2.0-M2.jar

If anyone wants to look at the simple project I created let me know and
I'll get you the source.

-Andy

> _____________________________________________ 
> 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?
> 
> -Andy
_______________________________________________
osee-dev mailing list
osee-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/osee-dev