Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Date: Thu, 23 Jul 2015 01:07:05 +0000 (UTC)
From: "Niclas Hedhman (JIRA)" <jira@apache.org>
To: dev@zest.apache.org
Message-ID: <JIRA.12843480.1436351679000.267045.1437613625659@Atlassian.JIRA>
In-Reply-To: <JIRA.12843480.1436351679000@Atlassian.JIRA>
References: <JIRA.12843480.1436351679000@Atlassian.JIRA>
 <JIRA.12843480.1436351679387@arcas>
Subject: [jira] [Resolved] (ZEST-47) Complex Configuration Types
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Niclas Hedhman resolved ZEST-47.
--------------------------------
    Resolution: Fixed

I want to close this for now, and retain the link to ZEST-105 when the ValueSerialization subsystem is redeisgned to take into account the Complex Types of configuration initialization.

> Complex Configuration Types
> ---------------------------
>
>                 Key: ZEST-47
>                 URL: https://issues.apache.org/jira/browse/ZEST-47
>             Project: Zest
>          Issue Type: New Feature
>            Reporter: Niclas Hedhman
>            Assignee: Niclas Hedhman
>             Fix For: 2.1
>
>
> See https://ops4j1.jira.com/projects/QI/issues/QI-350
> To allow complex Configuration types to be initialized from properties files.
> Since we now have ValueSerialization, I suggest that is used as an alternate configuration option to Properties files, so I can have YAML, XML or JSON as the static initialization format.


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