You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/27 06:44:04 UTC

[jira] [Commented] (CAMEL-5723) camel-jaxb: partClass and partNamespace dynamically set by header

    [ https://issues.apache.org/jira/browse/CAMEL-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986108#comment-15986108 ] 

ASF GitHub Bot commented on CAMEL-5723:
---------------------------------------

GitHub user onders86 opened a pull request:

    https://github.com/apache/camel/pull/1663

    CAMEL-5723 - set headers while setting partClass and partNamespace properties and update adoc

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/onders86/camel CAMEL-5723

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1663.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1663
    
----
commit 99942c8c03ca3a0635c9c785f21502fbfef3212c
Author: onders86 <on...@gmail.com>
Date:   2017-04-27T06:16:24Z

    CAMEL-5723 - set headers while setting partClass and partNamespace properties

commit ae986fe4d02360fa14712e119d53d39e6b8fbef4
Author: onders86 <on...@gmail.com>
Date:   2017-04-27T06:16:56Z

    CAMEL-5723 - update adoc

----


> camel-jaxb: partClass and partNamespace dynamically set by header
> -----------------------------------------------------------------
>
>                 Key: CAMEL-5723
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5723
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-jaxb
>            Reporter: Raúl Kripalani
>            Assignee: onder sezgin
>             Fix For: Future
>
>
> The Camel JAXB Data Format allows to specify a partClass and partNamespace on the data format configuration. 
> If you have many cases of partial marshalling or unmarshalling, you're forced to configure as many data formats as part classes you'll ever need to handle.
> Aside from being inconvenient, it makes route initialisation pretty inefficient because a JAXBContext is created per data format, performing a full scan and reflection of the package each time. Slows down route startup considerably.
> Enhance the Camel JAXB Data Format so that it's capable of doing partial unmarshalling at runtime based on message headers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)