[
https://issues.apache.org/jira/browse/IGNITE-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-3112:
-----------------------------------
Description:
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.
We can introduce top-level property merging to allow combining Spring and .NET
configs.
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.
was:Introduce IgniteConfiguration.MergeSpringConfig bool property.
> .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: Pavel Tupitsyn
> 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.
> We can introduce top-level property merging to allow combining Spring and
> .NET configs.
> 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)
