[
https://issues.apache.org/jira/browse/IGNITE-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861455#comment-15861455
]
Pavel Tupitsyn edited comment on IGNITE-4685 at 2/10/17 4:09 PM:
-----------------------------------------------------------------
{{PlatformAbstractBootstrap.start()}} reads configuration from platform side
and then starts Ignite. I see two ways of propagating configuration:
* Add {{IPluginConfiguration.WriteBinary(IBinaryRawReader)}} method and
{{IPluginConfiguration.PluginConfigurationClassName}} property. On Java side we
instantiate specified {{PluginConfiguration}} class and call constructor which
takes {{BinaryRawReader}}
* Platform provides a {{BinaryObject}} which is stored in
{{IgniteConfiguration}} and is later processed by {{PluginProvider}} when it
starts
was (Author: ptupitsyn):
{{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)
