Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Wed, 27 Jan 2016 18:11:40 +0000 (UTC)
From: "Luca Burgazzoli (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12676545.1383109923000.227488.1453918300715@Atlassian.JIRA>
In-Reply-To: <JIRA.12676545.1383109923000@Atlassian.JIRA>
References: <JIRA.12676545.1383109923000@Atlassian.JIRA>
 <JIRA.12676545.1383109923188@arcas>
Subject: [jira] [Resolved] (CAMEL-6913) Add dynamic unmarshalling capability
 to JiBX data format
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Luca Burgazzoli resolved CAMEL-6913.
------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: Future)
                   2.17.0

> Add dynamic unmarshalling capability to JiBX data format
> --------------------------------------------------------
>
>                 Key: CAMEL-6913
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6913
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jibx
>    Affects Versions: 2.12.1
>            Reporter: Strelok
>            Assignee: Luca Burgazzoli
>            Priority: Minor
>             Fix For: 2.17.0
>
>
> Currently a single instance of a JibxDataFormat supports unmarshalling a single class only as defined by the "unmarshallClass" attribute. If the application needs to be able to unmarshall to many classes an instance of a data format has to be created for every class which makes configuration tedious and verbose.
> Should be trivial to make the data format support dynamically choosing which unmarshall class to use via a header (CamelJibxUnmarshallClass for example).
> Creating this issue as a placeholder. I will try to submit a patch soon.


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