ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Tupitsyn <ptupit...@gridgain.com>
Subject Re: IgniteConfiguration.toXml()
Date Wed, 27 Jul 2016 07:23:56 GMT
So, no objections for adding this in .NET?

Another important use case is migrating from Spring XML (the only option in
1.5) to .NET XML (1.6+):
instead of rewriting config by hand, users can call
ignite.GetConfigurarion().ToXml() and copy the result.

On Tue, Jul 26, 2016 at 11:17 AM, Alexey Kuznetsov <akuznetsov@gridgain.com>
wrote:

> 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
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message