Re: [PROPOSAL] Apache Karaf Cave 5.0.0 version ?

[François Papon]

Hi JB,

+1 for all

I'm agree with the release version to 5.x as an internal transformation of Cave.

I'm ready to participate if you want some help :)

François

Le 17 mars 2018 17:25, Jean-Baptiste Onofré  a écrit :
>
> Hi guys, 
>
> I worked on a fairly large set of refactorings and improvements in 
> Apache Karaf Cave: 
>
> - usage of managed service for Cave repositories, with a service per 
> repo and a cfg file per repo 
> - in addition of the Maven "proxy" support, we now have support of Maven 
> for each repo 
> - OBR supports is now optional 
> - New shell commands and MBean to manipulate the Cave repositories from 
> a Maven perspective 
> - and much more 
>
> As those new features & improvements imply changes in the Cave 
> internals, I think it would be wise to bump the version to 5.0.0. 
>
> Thoughts ? 
>
> Thanks, 
> Regards 
> JB 

Re: Happy new year

[François Papon]

Thanks JB !

Happy new year to all the Karaf team !

Thank you for the Karaf project, the subprojects, the release, and the reply on 
the forum topics :)

François

Le 1 janv. 2018 11:08, Jean-Baptiste Onofré  a écrit :
>
> Hi all, 
>
> I wish you a happy and wonderful new year ! 
>
> Regards 
> JB 
> -- 
> Jean-Baptiste Onofré 
> jbono...@apache.org 
> http://blog.nanthrax.net 
> Talend - http://www.talend.com 

Re: [Decanter] - Collector socket marshaller improvement

[François Papon]

Yes, that's it :)

Le 3 nov. 2017 12:30, Jean-Baptiste Onofré <j...@nanthrax.net> a écrit :
>
> That's before the socket appender sends json. So you are talking about 
> unmarshaller, not marshaller. The socket collector receives json data and 
> transforms to a map. That's normal and the expected behavior. 
>
> If you want to be able to change the unmarshaller, that makes sense. 
>
> Regards 
> JB 
>
> On Nov 3, 2017, 09:18, at 09:18, "François Papon" 
> <francois.pa...@openobject.fr> wrote: 
> >Ok, I miss something, because I see the unmarshall method in the 
> >collector and for me it take json and transform it to a Map. I would 
> >explain that how could the collector take another format than json from 
> >the socket inputstream reader. 
> > 
> >Le 3 nov. 2017 12:08, Jean-Baptiste Onofré <j...@nanthrax.net> a écrit : 
> >> 
> >> See my last e-mail in the thread. 
> >> 
> >> The collector should only send map. Marshaller should be called by 
> >the appender. 
> >> 
> >> That's really important to both decouple collectors and appenders and 
> >be able to use the alerts checker. 
> >> 
> >> Regards 
> >> JB 
> >> 
> >> On Nov 3, 2017, 09:05, at 09:05, Francois Papon 
> ><francois.pa...@openobject.fr> wrote: 
> >> >We also have to change the target of the @Reference unmarshaller in 
> >the 
> >> >SocketCollector 
> >> > 
> >> >@Reference(target=Marshaller.SERVICE_KEY_DATAFORMAT + 
> >> >"=my-data-format") 
> >> >    public void setUnmarshaller(Unmarshaller unmarshaller) { 
> >> >    this.unmarshaller = unmarshaller; 
> >> >    } 
> >> > 
> >> >where my-data-format is a config propertie, may be the reference 
> >have 
> >> >to 
> >> >be set in the activate method. 
> >> > 
> >> >Le 03/11/2017 à 11:56, Francois Papon a écrit : 
> >> >> 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. 
> >> >> 

Re: [Decanter] - Collector socket marshaller improvement

[François Papon]

Ok, I miss something, because I see the unmarshall method in the collector and 
for me it take json and transform it to a Map. I would explain that how could 
the collector take another format than json from the socket inputstream reader.

Le 3 nov. 2017 12:08, Jean-Baptiste Onofré  a écrit :
>
> See my last e-mail in the thread. 
>
> The collector should only send map. Marshaller should be called by the 
> appender. 
>
> That's really important to both decouple collectors and appenders and be able 
> to use the alerts checker. 
>
> Regards 
> JB 
>
> On Nov 3, 2017, 09:05, at 09:05, Francois Papon 
>  wrote: 
> >We also have to change the target of the @Reference unmarshaller in the 
> >SocketCollector 
> > 
> >@Reference(target=Marshaller.SERVICE_KEY_DATAFORMAT + 
> >"=my-data-format") 
> >    public void setUnmarshaller(Unmarshaller unmarshaller) { 
> >    this.unmarshaller = unmarshaller; 
> >    } 
> > 
> >where my-data-format is a config propertie, may be the reference have 
> >to 
> >be set in the activate method. 
> > 
> >Le 03/11/2017 à 11:56, Francois Papon a écrit : 
> >> 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. 
> >>