Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
Date: Tue, 23 Dec 2014 11:50:13 +0000 (UTC)
From: "J.P. Koek (JIRA)" <jira@apache.org>
To: dev@curator.apache.org
Message-ID: <JIRA.12763447.1419335403000.90712.1419335413119@Atlassian.JIRA>
In-Reply-To: <JIRA.12763447.1419335403000@Atlassian.JIRA>
References: <JIRA.12763447.1419335403000@Atlassian.JIRA>
 <JIRA.12763447.1419335403255@arcas>
Subject: [jira] [Created] (CURATOR-174) Incompatible types between
 curator-rpc and the other elements
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

J.P. Koek created CURATOR-174:
---------------------------------

             Summary: Incompatible types between curator-rpc and the other elements
                 Key: CURATOR-174
                 URL: https://issues.apache.org/jira/browse/CURATOR-174
             Project: Apache Curator
          Issue Type: Wish
          Components: Framework
    Affects Versions: 2.7.0
         Environment: Windows C# / Java / Zookeeper
            Reporter: J.P. Koek
            Priority: Minor
             Fix For: awaiting-response


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 module.

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
(v6.3.4#6332)