camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Proctor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-2915) Support more XStream configurations
Date Thu, 08 Jul 2010 13:52:52 GMT

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

Mark Proctor commented on CAMEL-2915:
-------------------------------------

"I could probably look in the XStream documentation, but I wonder what you need all those
additional options for? Is it for fine grained control of the mapping?
And in which situations would you use that, over the default convention over configuration?"

The default xstream output is pretty verbose, these are the main configurations I use when
customising the format of xml. We have put a lot of effort into trying to create an xml which
is more user friendly.

"I noticed you added a driver option to the xstream data format.

Btw the json data format has a type option you can chose the library being used

    * XStream (default)
    * Jackson"

The existing json format uses xstream, but it is not tied to it. As such it would not make
sense to start to add xstream specific configurations to that data format definition; they
would not be relevant if you selected jackon. So if I want to use xstream's json but I want
to have some mapping configurations, it will need to be done as part of the xstream dataformatdefinition.

> Support more XStream configurations
> -----------------------------------
>
>                 Key: CAMEL-2915
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2915
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core, camel-xstream
>            Reporter: Mark Proctor
>            Assignee: Hadrian Zbarcea
>             Fix For: 2.4.0
>
>         Attachments: camel-core.diff, camel-xstream.diff
>
>
> Current the XStream DataFormatDefinition cannot be configured, beyond encoding. At a
minimum it shoul support Converters, Aliases an Implicit Collections.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message