[
https://issues.apache.org/jira/browse/IGNITE-6272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198368#comment-16198368
]
Alexey Popov commented on IGNITE-6272:
--------------------------------------
[~ptupitsyn] Please review the fixes in commits:
https://github.com/apache/ignite/pull/2813/commits/4f8bc279d268679ea13599673f3fd8690ade6474
https://github.com/apache/ignite/pull/2813/commits/47a71965257dc8cb92a24a4c87be137d4a97c9f7
1. All review findings are fixed.
2. All test cases passed locally, TC is in progress
Changes description:
1. Now java code (all {{deploy*}} methods) passes failed configurations back to
.NET code. It is done at {{PlatformServices.writeDeploymentResult()}}. There
were some minor changes in {{PlatformDotNetServiceImpl}} and
{{PlatformClusterNodeFilterImpl}} to get the original Service and Filter for
serialization
2. .NET code {{ServiceProxySerializer.ReadDeploymentResult}} reads serialized
failed configurations and adds them to {{ServiceDeploymentException}}
> .NET: Propagate multiple services deployment
> --------------------------------------------
>
> Key: IGNITE-6272
> URL: https://issues.apache.org/jira/browse/IGNITE-6272
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Reporter: Denis Mekhanikov
> Assignee: Alexey Popov
> Labels: .NET, newbie
> Fix For: 2.4
>
>
> Multiple services deployment support should be propagated to .NET:
> * {{IgniteServices.deployAll}}
> * {{IgniteServices.deployAllAsync}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
