[
https://issues.apache.org/jira/browse/IGNITE-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285992#comment-15285992
]
ASF GitHub Bot commented on IGNITE-3112:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/706
> .NET: Allow merging Spring XML config with .NET config
> ------------------------------------------------------
>
> Key: IGNITE-3112
> URL: https://issues.apache.org/jira/browse/IGNITE-3112
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Affects Versions: 1.6
> Reporter: Pavel Tupitsyn
> Assignee: Vladimir Ozerov
> Priority: Critical
> Fix For: 1.6
>
>
> Currently we ignore most IgniteConfiguration properties if SpringConfigUrl is
> set.
> So if there is even one property not propagated to .NET, user has to switch
> completely to Spring XML, which may be quite tragic, especially for query
> entity configurations.
> Instead, we can merge configs on the top level:
> First, we load Spring XML. Then we apply non-null .NET properties on top of
> it.
> Primitive properties should be made nullable underneath to track whether user
> has set them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
