Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CAK2_iMPu2T0pQO9AMgCfUN=kN+WpC8jFq6=cyXwmRvRrbCpu0Q@mail.gmail.com>
References: <CAK2_iMPu2T0pQO9AMgCfUN=kN+WpC8jFq6=cyXwmRvRrbCpu0Q@mail.gmail.com>
From: Alexey Kuznetsov <akuznetsov@gridgain.com>
Date: Tue, 26 Jul 2016 15:17:21 +0700
Message-ID: <CALH+G9ptFMyFkNs=svk2w-yQ8rjchq3PDrKpny-04t6DY8dbMA@mail.gmail.com>
Subject: Re: IgniteConfiguration.toXml()
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a1142c240b60f440538858782
archived-at: Tue, 26 Jul 2016 08:17:28 -0000

--001a1142c240b60f440538858782
Content-Type: text/plain; charset=UTF-8

Pavel,

In Web Console [1] we have generation of Spring XML and appropriate Java
code generation.
And from my experience it is not trivial thing to generate Spring XML in
some cases (if we will write code by ourselves).

If we will use Spring marshaling - that will bring a dependency from Spring
 to ignite-core and we cannot do this.
We could add this as utility method to ignite-spring module.

[1]. https://ignite.apache.org/addons.html#web-console


On Tue, Jul 26, 2016 at 2:19 PM, Pavel Tupitsyn <ptupitsyn@apache.org>
wrote:

> Igniters,
>
> This applies equally to Java and .NET:
>
> Writing XML configuration in not easy or fun. I've seen lots of questions
> on how to configure things in XML.
> Spring syntax is cumbersome even when you get used to it.
>
> On the other hand, setting IgniteConfiguration properties directly in Java
> or C# is much easier because of the IDE support.
> Sometimes users will start with a code-only app and decide to move
> configuration to XML.
>
> So I propose to add IgniteConfiguration.toXml() method in Ignite.NET.
> Not sure how easy it is in Java, but .NET already has it, just hidden from
> public API.
>
> Thoughts? Objections?
>
> Pavel.
>


-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

--001a1142c240b60f440538858782--