[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] JMS providers, JGroups providers, ECF servers (oh my)

Hi Chris,

Chris Aniszczyk wrote:

Cool stuff, I think this is ECF blog-worthy Scott ;)


Yes, indeed...will do so!

Scott



Cheers,

---
Chris Aniszczyk | IBM Lotus | Eclipse Committer | http://mea-bloga.blogspot.com | +1.860.839.2465

Inactive hide details for Scott Lewis ---09/04/2007 02:39:54 AM---Hi Folks, In order to expand the usefulness of ECF, for both Scott Lewis ---09/04/2007 02:39:54 AM---Hi Folks, In order to expand the usefulness of ECF, for both Equinox-based servers


From:

Scott Lewis <slewis@xxxxxxxxxxxxx>

To:


Cc:

"Eclipse Communication Framework (ECF) developer mailing list." <ecf-dev@xxxxxxxxxxx>

Date:

09/04/2007 02:39 AM

Subject:

[ecf-dev] JMS providers, JGroups providers, ECF servers (oh my)





Hi Folks,

In order to expand the usefulness of ECF, for both Equinox-based servers
and clients, I've created ECF providers using two Java Messaging Service
(JMS) implementations:

1) ActiveMQ/Websphere CE
2) BEA Weblogic

These two JMS implementation plugins are based upon plugin
(org.eclipse.ecf.provider.jms) that uses a JMS topic to communicate.
These two JMS-implementation-specific plugins are very thin, and are
easily duplicated for other JMS implementations.  As per this
enhancement request:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=187654, I am going to add
one more JMS implementation based upon Net4j.

Each of these providers defines both a server container and a client
container, and each also exposes an IApplication instance for
starting/running via Equinox rather than Eclipse.

Also, I've implemented an ECF provider based upon JGroups
(
www.jgroups.org) a java-implemented messaging API that uses reliable
multicast for peer-to-peer communication.  This makes it possible to run
an ECF generic client with no server, with efficient and reliable
peer-to-peer communication.

Any applications built upon ECF datashare API, shared object API, or
remote services API will work unmodified on this topology, as well as
the JMS providers above or the ECF generic server.

The plugins will exist at the ECF OSU OSL site, at least for the near
future, because they depend upon libraries that are under licenses
incompatible with the EPL.  I hope to have them in the build for binary
distribution by this Friday (Sept 7) ECF 1.1 release.

Please let me know if you have any questions or comments.  See here:
http://ecf1.osuosl.org for info about accessing the source code.

Scott



_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev


_______________________________________________ ecf-dev mailing list ecf-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ecf-dev

GIF image

GIF image