Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Sun, 17 Jul 2016 05:39:20 +0000 (UTC)
From: "Milap Wadhwa (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12920108.1449588245000.52082.1468733960479@Atlassian.JIRA>
In-Reply-To: <JIRA.12920108.1449588245000@Atlassian.JIRA>
References: <JIRA.12920108.1449588245000@Atlassian.JIRA> <JIRA.12920108.1449588245658@arcas>
Subject: [jira] [Assigned] (IGNITE-2112) Provide a way to
 serialize/deserialize an IgniteConfiguration object using JSON
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 17 Jul 2016 05:39:22 -0000


     [ https://issues.apache.org/jira/browse/IGNITE-2112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Milap Wadhwa reassigned IGNITE-2112:
------------------------------------

    Assignee: Milap Wadhwa

> Provide a way to serialize/deserialize an IgniteConfiguration object using JSON
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-2112
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2112
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: ignite-1.4
>            Reporter: Juan Velez
>            Assignee: Milap Wadhwa
>            Priority: Minor
>
> Currently as of Release 1.4, Ignite does not provide a way to serialize/deserialize an IgniteConfiguration object using JSON. Attempts to create a working serializer/deserializer are met with very difficult setup and configuration because the IgniteConfiguration (and subcomponents) rely on Factories, SPIs, etc for properties. as well as not being completely compliant with the JavaBeans standard.
> It would be great if the serialization/deserialization using JSON could be provided as either a new method in an existing/new Util class or part of the IgniteConfiguration class itself.
> I understand that in the case of deserialization most likely there would be constraints on how to correctly specify the JSON string but that would be left for implementors of the feature to correctly decide/design/document.
> See user@ thread http://apache-ignite-users.70518.x6.nabble.com/How-to-serialize-deserialize-IgniteConfiguration-to-from-JSON-td2164.html


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)