[
https://issues.apache.org/jira/browse/CHAIN-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568048#comment-13568048
]
Onur GUNDURU commented on CHAIN-76:
-----------------------------------
I'm quite new to apache commons chain, just saw the post in jackson forum while
trying to implement a builder api. Actually i have no idea where/how to start,
need to look around for a while :) Jackson deserialization can be done using
modules. I do use deserialization for polymorphic types. Is it configuration
parameters that you need to deserialize and/or chains?
http://wiki.fasterxml.com/JacksonPolymorphicDeserialization
> Adopt Jackson as underlying parser for Configurations
> -----------------------------------------------------
>
> Key: CHAIN-76
> URL: https://issues.apache.org/jira/browse/CHAIN-76
> Project: Commons Chain
> Issue Type: Task
> Affects Versions: 2.0
> Reporter: Simone Tripodi
> Fix For: 2.0
>
> Attachments: CHAIN-76_proto.patch
>
>
> [Jackson|http://wiki.fasterxml.com/JacksonHome] supports data format
> [auto-detection|http://www.cowtowncoder.com/blog/archives/2012/04/entry_472.html]
> for formats such as JSON, XML, Smile and YAML, so it would be possible that
> with just one {{ConfigurationParser}} implementation we are able to handle
> multiple textual configuration formats.
> In that way we can stay with just one module for configuration and no more
> need to implement a specific module for each desired format.
--
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
