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

["Pascal Schumacher (JIRA)" <ji...@apache.org>]

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

Pascal Schumacher commented on CAMEL-5723:
------------------------------------------

The fix version for this (and probably other issues fixed between the two release candidates for 2.19) should be 2.19 (see: https://github.com/apache/camel/commits/camel-2.19.x). 

> 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: 2.20.0
>
>
> 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)