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

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2020/04/02 10:44:00 UTC

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

     [ https://issues.apache.org/jira/browse/IGNITE-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Tupitsyn reassigned IGNITE-10075:
---------------------------------------

    Assignee: Pavel Tupitsyn  (was: Alexey Kukushkin)

> .NET: 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: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET, sbcf
>         Attachments: ignite-10075-vs-2.8.patch
>
>
> 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
(v8.3.4#803005)