[
https://issues.apache.org/jira/browse/IGNITE-2686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206158#comment-15206158
]
Pavel Tupitsyn edited comment on IGNITE-2686 at 3/22/16 10:56 AM:
------------------------------------------------------------------
1) Fixed
2) The same problem is on .NET side. We can cache methods only when there is no
ambiguity (only one method with a given name and arg count).
3) varargs/params are just an array underneath. Tests are already there, see
ServicesTest.cs:574 and PlatformDeployServiceTask.java:305
was (Author: ptupitsyn):
1) Fixed
2) The same problem is on .NET side. We can cache methods only when there is no
ambiguity (only one method with a given name and arg count).
3) varargs/params are just an array underneath. Tests are already there, see
ServicesTest.cs:574 and PlatformDeployServiceTask:305
> .NET: Call Java services
> ------------------------
>
> Key: IGNITE-2686
> URL: https://issues.apache.org/jira/browse/IGNITE-2686
> Project: Ignite
> Issue Type: New Feature
> Components: managed services, platforms
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> Add support for Java service calls (see OP_DOTNET_INVOKE in PlatformServices).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)