Hi Cesar,
thanks for the reply and very nice to see you here.
In fact, we are currently working on something which seems to be similar to
what I see in your Blog about "Merlot".
I will have a deeper look and come back to you with questions : )
And regarding your comment, of course we have to be compliant to the compendium
spec, but generally AFAIR there are two ways to have OSGi-ready bundles.
First is to add the MANIFEST.MF in the original jar then its both, a jar and a
bundle.
Or add a "jar" on top (which only consitst of a pom as Module) and specifies
the Imports / exports for BND to generate the jar with the code (and probably
some nested jars).
This is what I was referring to.
Both approaches should lead to compliant OSGi Bundles, in my understanding, or?
Julian
Am 07.10.19, 16:32 schrieb "César García" <cesar.gar...@ceos.com.ve>:
Hello everyone,
First of all, cordial greetings to the entire PLC4X team, I am very happy
to see this project working and I hope to collaborate on it.
Regarding the integration of PLC4X with Karaf (aka OSGI), I think we need
follow the path specified by the standard, as indicated in the Compendium
document, Charter 103. I put a short summary in this blog [1].
Karaf is an excellent tool, and a while ago I developed a communications
gateway for Apacs, S7 and Modbus with Karaf version 2, all running 24/7 in an
OIL & Gas plant.
I will work to make part of that code in PLC4X at some point.
Regards,
1. Http://glcj.blogspot.com
2.
Enviado desde mi BlackBerry, el dispositivo móvil más seguro
Mensaje original
De: j.feina...@pragmaticminds.de
Enviados: 7 de octubre de 2019 10:07
Para: dev@plc4x.apache.org
Responder a: dev@plc4x.apache.org
Asunto: PLC4X and OSGi
Hi all,
as some of you may have notices from Twitter or Slack I am currently
working on integrating PLC4X into OSGi and especially Karaf.
I get a lot of help from the Karaf guys and also Lukasz joined the effort
to get this done, finally : )
For the Drivers, there is one “central” question.
Do we want the Driver jars to also be OSGi-Bundles or do we prefer separate
jars with a 1-1 relationship as OSGi bundles.
Other projects, like Netty do it all in one
(https://netty.io/wiki/new-and-noteworthy-in-4.0.html).
In fact, the only difference is a “META-INF/MANIFEST.MF” file which is
there additionally. So it hurts nobody but helps OSGi users.
What are your thoughts on that?
Julian
