curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jordan Zimmerman (JIRA)" <>
Subject [jira] [Commented] (CURATOR-174) Incompatible types between curator-rpc and the other elements
Date Mon, 20 Apr 2015 23:49:59 GMT


Jordan Zimmerman commented on CURATOR-174:

I don't know what the proxy can do. ServiceInstances are serialized with JsonInstanceSerializer.
In C# you can deserialize the payload with the C# JSON deserializer and vice-versa when creating
new payloads. I just tried this with the TestClient and it works.

> Incompatible types between curator-rpc and the other elements
> -------------------------------------------------------------
>                 Key: CURATOR-174
>                 URL:
>             Project: Apache Curator
>          Issue Type: Wish
>          Components: Framework
>    Affects Versions: 2.7.0
>         Environment: Windows C# / Java / Zookeeper
>            Reporter: J.P. Koek
>            Assignee: Jordan Zimmerman
>            Priority: Minor
>             Fix For: 2.7.2
> I'm using the curator-x-rpc module to connect Microsoft C# with zookeeper.
> In my Java application I'm using a specific InstanceDetails object which is used in the
payload of the instance.
> If I'm using the curator-rpc module the data is set to byte[] which is not the case for
my Java object, which is streamed with the JsonInstanceSerializer (default).
> By having this I'm not able to register an service through the curator-x-rpc module and
then use it in my java application.
> The same problem occurs with the java TestClient which is part of the test set of the
> Also the created instances with the Java instances can't be used by the curator-x-rpc
because of the missing InstanceDetails class.

This message was sent by Atlassian JIRA

View raw message