camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raul Kripalani (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5723) camel-jaxb: partClass and partNamespace dynamically set by header
Date Sat, 20 Oct 2012 16:26:11 GMT

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

Raul Kripalani updated CAMEL-5723:
----------------------------------

    Description: 
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.

  was:
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 force to configure
as many data formats as part classes.

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.

Enhance the Camel JAXB Data Format so that it's capable of doing partial unmarshalling at
runtime based on message headers.

    
> 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: Raul Kripalani
>            Assignee: Raul Kripalani
>             Fix For: 2.11.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message