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 2017/02/10 16:03:42 UTC

[jira] [Commented] (IGNITE-4685) Propagate platform plugin configuration to Java

    [ https://issues.apache.org/jira/browse/IGNITE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861455#comment-15861455 ] 

Pavel Tupitsyn commented on IGNITE-4685:
----------------------------------------

{{PlatformAbstractBootstrap.start()}} reads configuration from platform side and then starts Ignite. I see two ways of propagating configuration:

* Platform provides a class name which we instantiate and call some method which deserializes plugin configuration and updates {{PluginConfiguration}}, like we update {{IgniteConfiguration}} via {{PlatformConfigurationUtils}}
* Platform provides a {{BinaryObject}} which is stored in {{IgniteConfiguration}} and is later processed by {{PluginProvider}} when it starts

> Propagate platform plugin configuration to Java
> -----------------------------------------------
>
>                 Key: IGNITE-4685
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4685
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: platforms
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>              Labels: .NET
>             Fix For: 2.0
>
>
> {{IPluginConfiguration}} implementations should be able to propagate data to Java side and update corresponding {{PluginConfiguration}} there.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)