Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Zookeeper Discovery Examples released to HEAD

Hi Folks,

Congratulations to Ahmed, Wim and others are in order for this contribution. Addition of Zookeeper-based discovery...all the way through to the working OSGi remote services hello examples...represents a great achievement. It shows the power of ECF's modular approach to remote services...the ability to mix and match discovery protocols (SLP, Zeroconf, Zookeeper, dns-sd, xml file, etc) with distribution providers (rosgi, ecf generic, jms, rest, soap, etc) to instantly produce an OSGi standards-compliant remote services implementation that matches your specific needs for interoperability, security, performance, etc.

I've done a Helios build using these changes/additions, and it's available for test download/install here:

http://download.eclipse.org/rt/ecf/3.3/helios/site.p2

Thanks!

Scott

Wim Jongman wrote:
Hello All,

Ahmed, Scott and myself have been busy with the zookeeper examples
which have been released to HEAD. Get the o.e..hello.host and
o.e..hello.consumer bundles along with the ..zookeeper bundles. Open
the zookeeper,generic product files in the products directory of both
example bundles and select 'Run as Eclipse Application' on both
product files.

You will see that the service gets published on the host VM and
discovered in the consumer VM. After discovery on the consumer VM the
service gets activated with both direct/blocking and async/not
blocking service calls. Which is Uber Cool (if you like these kind of
things :).

We also have configurations for r_osgi, see the appropriate product
configurations and start them.

We have restyled the examples for clarity and we have added a command
provider. This command provider supplies the "hello" command to the
equinox console:

hello stop: will stop the host bundle if not already stopped.
hello start: will start the host bundle if not already started.

You will see publication and discovery events flying by in the console.

The org.apache.zookeeper bundle contains a log4j config in the conf
directory. It is switched off by default. Replace the line that reads
log4j.appender.CONSOLE.Threshold=ERROR by
log4j.appender.CONSOLE.Threshold=INFO to start logging after
restarting both product.

We will be starting a blog series about the capabilities off the
zookeeper discovery provider and be updating the example wiki page as
well.

Please try the examples and report any problems.

Best regards

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


Back to the top