karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KARAF-4303) Create decanter marshalling services
Date Wed, 03 Feb 2016 19:53:39 GMT

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

Christian Schneider resolved KARAF-4303.
    Resolution: Fixed

> Create decanter marshalling services
> ------------------------------------
>                 Key: KARAF-4303
>                 URL: https://issues.apache.org/jira/browse/KARAF-4303
>             Project: Karaf
>          Issue Type: New Feature
>          Components: decanter
>    Affects Versions: decanter-1.0.1
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Christian Schneider
>             Fix For: decanter-1.0.2
> The decanter collectors collect the data as a key/value pair data (Map).
> The decanter appenders directly uses this Map to store on the backend (it's the case
for Camel and ActiveMQ appenders), but other appenders marshall this Map as a JSON string
(it's the case of the Elasticsearch or JDBC appenders).
> As a good design improvement, we can provide a DecanterMarshaller interface that convert
this Map as a Object. We can implement a first JSONDecanterMarshaller service (we can imagine
to provide new marshallers later). The appenders can "filter" to pick the marshaller he wants
to use or just use one service (when multiple).

This message was sent by Atlassian JIRA

View raw message