You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/07/11 15:36: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=14623393#comment-14623393 ]
Claus Ibsen commented on CAMEL-5723:
------------------------------------
You can use the data format component and use a "dynamic to". But yeah maybe also nicer to improve jaxb dataformat to support a header to control the behavior.
> 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
> 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.4#6332)