karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4303) Create decanter marshalling services
Date Mon, 01 Feb 2016 14:41:39 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126310#comment-15126310

ASF subversion and git services commented on KARAF-4303:

Commit 355aa8337c1045d1a26a25346cb4588cac3185fa in karaf-decanter's branch refs/heads/master
from [~chris@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-decanter.git;h=355aa83 ]

[KARAF-4303] Create decanter marshalling services

> 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
> 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