Both approaches are independent of OSGi framework implementations, which is
part of the beauty of OSGi.
Lukasz puts more value on some dogmatic principle ("only interfaces in
API"), whereas I have forwarded how an OSGi bundle producer is expected to
provide it, and how an OSGi bundle consumer
Turker TUNALI created PLC4X-196:
Summary: Apache NiFi integration should allow Expression Language
Project: Apache PLC4X
I have to admit that I would prefer this option ... but we should also let the
others state their opinion.
Am 07.05.20, 19:27 schrieb "Etienne Robinet" <43...@etu.he2b.be>:
Well then we could create a seperate module to put the Activators we have
ottobackwards opened a new pull request #151:
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
so if there is an option that doesn't tie our API and Drivers to a specific
OSGi framework, I would prefer that.
Am 07.05.20, 12:35 schrieb "Julian Feinauer" :
I would say that there are arguments for both cases (as ist often with
So I see them not as
I'm Etienne, 24 years old (2 weeks until 25) and I'm currently studying
Computer Science with a focus on Industrial IT in Brussels. I'm in my last
semester and doing an Internship in Luxembourg, the country I live in,
where I have been assigned to work with PLC and monitoring data using
I would say that there are arguments for both cases (as ist often with OSGi,
So I see them not as right or wrong but as to different styles or approaches
that I woudl leave up to you to decide.
Am 07.05.20, 10:07 schrieb "Robinet, Etienne" <43...@etu.he2b.be>:
first, thanks for starting this excellent initiaive (we should probably place
the texts even on the "team" part oft he homepage).
I am Julian, 32 years old, married to my lovely wide Constanze and have three
kids (two of them know toddy personally and like him, the third is too
I am a research assistant at the University of Stuttgart at the Institute of
Control Engineering (ISW) and work there in the areas of communication/service
concepts for automation systems and cloud manufacturing.
Among other things with projects like RetroNet I got in contact with several
As I am really not an expert, which approach should we use?
Le mer. 6 mai 2020 à 15:57, Łukasz Dywicki a écrit :
> Hey Niclas,
> While this code seems straight I don't think it is needed, and valid in
> our case.
> Main benefit of extender and extender based patterns is
Mail list logo