You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Alexey Kukushkin (JIRA)" <ji...@apache.org> on 2018/10/30 23:55:00 UTC

[jira] [Created] (IGNITE-10075) Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET

Alexey Kukushkin created IGNITE-10075:
-----------------------------------------

             Summary: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
                 Key: IGNITE-10075
                 URL: https://issues.apache.org/jira/browse/IGNITE-10075
             Project: Ignite
          Issue Type: Improvement
          Components: platforms
    Affects Versions: 2.6
            Reporter: Alexey Kukushkin
            Assignee: Alexey Kukushkin


Presently if there is an Ignite Java service taking parameters of complex (composite) types and returning a result of complex type then all the complex types must be explicitly specified in the binary configuration.

We need to enhance Ignite not to require binary configuration assuming that we use the same type, package/namespace and field/property names on both the .NET and Java sides (or provide a custom name mapper for relaxed naming conventions).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)