karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: [Decanter] - Collector socket marshaller improvement
Date Fri, 03 Nov 2017 08:03:44 GMT
Hi

No it's not a good idea. The collector doesn't del with marshalling. It should send only data
as a map.
The marshaller is at appender level.

Regards
JB

On Nov 3, 2017, 08:56, at 08:56, Francois Papon <francois.papon@openobject.fr> wrote:
>Hi,
>
>I'm back with Decanter :)
>
>I'm thinking about adding a new propertie in the collector-socket to
>define wich marshaller to use.
>
>Actually, the collector-socket marshaller work's only with Json format
>in input but it will be nice if other format could be support.
>
>In the case of network equipement, data is send in different format,
>and
>most of the time, each constructor send data in proprietary format.
>
>We could made custom dataFormatter implement Marshaller/Unmarshaller
>decanter API packaging in a bundle as the Decanter Marshall Json,
>declare like :
>
>@Component(
>    immediate = true,
>    property = Marshaller.SERVICE_KEY_DATAFORMAT + "=my-data-format"
>)
>
>in the properties cfg of the collector-socket we could add :
>
># Dataformat json(default)
>#dataformat=json
>
>dataformat=my-data-format
>
>I'm ready to do it if you think it could be reuse.

Mime
  • Unnamed multipart/alternative (inline, 7-Bit, 0 bytes)
View raw message