You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Jordan Zimmerman (JIRA)" <ji...@apache.org> on 2015/04/19 19:35:00 UTC
[jira] [Assigned] (CURATOR-174) Incompatible types between
curator-rpc and the other elements
[ https://issues.apache.org/jira/browse/CURATOR-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jordan Zimmerman reassigned CURATOR-174:
----------------------------------------
Assignee: Jordan Zimmerman
> 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
> Assignee: Jordan Zimmerman
> 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)