[
https://issues.apache.org/jira/browse/CAMEL-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Posta updated CAMEL-6677:
-----------------------------------
Attachment: CAMEL-6677-2.patch
Claus,
looking for feedback here. data formats don't have good access to the camel
context (unless in the data format itself, which not all have), so looking up
beans can be hit or miss depending on the data format used. For jaxb it works
fine. See revised patch and give suggestions. Check the changes I made for
DataFormatDefinition. It correctly resolves refNames that start with '#' but
not very pretty :) All tests pass...
> Allow customization of the JAXB underlying XMLStreamWriter
> ----------------------------------------------------------
>
> Key: CAMEL-6677
> URL: https://issues.apache.org/jira/browse/CAMEL-6677
> Project: Camel
> Issue Type: Improvement
> Components: camel-jaxb
> Affects Versions: 2.11.1
> Reporter: Christian Posta
> Priority: Minor
> Fix For: 2.11.2, 2.12.1
>
> Attachments: CAMEL-6677-2.patch, CAMEL-6677.patch
>
>
> Right now the jaxb component allows you to filter out non-xml characters. But
> there might be use cases where you'd want to do something other than just
> filter (maybe escape?
> http://blog.lesc.se/2009/03/escape-illegal-characters-with-jaxb-xml.html or
> replace with something else?) the non-xml characters. JAXB has a mechanism to
> allow pre-processing of the output of its marshaling and we should expose a
> way to customize that.
--
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
