Re: [ecf-dev] Zookeeper Discovery Examples released to HEAD

[Wim Jongman <wim.jongman@xxxxxxxxx>]

Fixed and released to HEAD

Thanks for reporting.

On Tue, May 25, 2010 at 11:34 AM, Patrick D. <pd4ecf@xxxxxxxxxxxxxx> wrote:
> Hello guys.
> Thank you for working on the hello world examples.
> I had problems when running them, though.
> Whichever product file I started, an exception like the following was always
> thrown:
> java.lang.NullPointerException
> at
> org.eclipse.ecf.provider.zookeeper.core.internal.Configuration.clean(Configuration.java:220)
> at
> org.eclipse.ecf.provider.zookeeper.core.internal.Configuration.configure(Configuration.java:64)
> at
> org.eclipse.ecf.provider.zookeeper.core.ZooDiscoveryContainer.init(ZooDiscoveryContainer.java:119)
> at
> org.eclipse.ecf.provider.zookeeper.core.ZooDiscoveryContainer.connect(ZooDiscoveryContainer.java:339)
> at
> org.eclipse.ecf.provider.zookeeper.DiscoveryActivator$3.run(DiscoveryActivator.java:136)
> at java.lang.Thread.run(Thread.java:619)
>
> Digging a bit through the code I found out that the problem is the
> setZookeeperData call in Configuration.java:57. It always tried to create
> the path "/tmpzookeeperData". Of course, it has rights to create a directory
> in my root.
> Adding a "+ File.separatorChar" and thus changing the call to
> setZookeeperData(new File(getConfigProperties().get(
> ZOOKEEPER_TEMPDIR).toString() + File.separatorChar
> + getConfigProperties().get(ZOOKEEPER_DATADIR)));
>
> fixed the problem.
> Forgive me if this is not the right way to inform you of the bug and fix. ;)
> Thanks and Regards,
> Patrick
>
> On Wed, May 19, 2010 at 11:53 AM, Wim Jongman <wim.jongman@xxxxxxxxx> 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
>
>
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>
>