Hi Julian, that actually did the trick. But now I am getting the next error. https://i.imgur.com/U7NjmsF.png As you can see, the class it cant find is inside the container, so that is even more weird.
Etienne On 2020/03/31 14:09:11, Julian Feinauer <j.feina...@pragmaticminds.de> wrote: > Hi, > > this is not so optimal. > Then one solution would be to embed the SPI bundle inside the transport > bundle(s). > This can be done with the felix-maven plugin by using the > <Embed-dependencies> configuration if I remember correctly. > > Julian > > Am 31.03.20, 16:07 schrieb "Etienne Robinet" <43...@etu.he2b.be>: > > Hi, > From the log the class is called outside the SPI by the transport > > Etienne > > > Le 31 mars 2020 à 15:24, Julian Feinauer <j.feina...@pragmaticminds.de> > a écrit : > > > > Hi, > > > > yes, if ist only needed internally its fine.But why does someone then > get a Class Not Found Exception? > > This is usually a hint to some class loader issue in OSGi which is > related to exports/ imports. > > > > J > > > > Am 31.03.20, 15:23 schrieb "Christofer Dutz" > <christofer.d...@c-ware.de>: > > > > As this package is only referenced from within SPI, couldn't we just > exclude it from the package exports? > > > > Chris > > > > Am 31.03.20, 15:17 schrieb "Julian Feinauer" > <j.feina...@pragmaticminds.de>: > > > > Hi, > > > > the issue is that if we export it, then we break Nettys OSGi > integration as we get a split package situation (two bundles exporting the > same package, which is forbidden in OSGi). > > > > So I see no easy solution (but had to do the same once as Netty > is pretty... private). > > > > J > > > > Am 31.03.20, 15:15 schrieb "Christofer Dutz" > <christofer.d...@c-ware.de>: > > > > Hi all, > > > > I just discussed this issue with Etienne and I thought it > was important for all, so I asked him to bring it here. > > > > In my effort to get the EmbeddedChannel working as a full > "transport" module, I had to override the Netty Bootstrap mechanism. > > Unfortunately in order to do so, I need to call "init" from > the derived class. Unfortunately this is package private in Netty so I had > > To add it to the same package. > > > > Would it help to just not export these packages to OSGi? > > > > But I'm also open for alternatives (Please none involving > mega-evil reflection hackery). > > > > > > Chris > > > > Am 31.03.20, 15:10 schrieb "Etienne Robinet" > <erobi...@apache.org>: > > > > Hi all, > > I've been working on the Camel Component and decided to > test it inside Karaf, but I noticed that I've got this error now: > > https://i.imgur.com/kUZPwZ5.png > > > > Seems like this class is not exported by the bundle so > it can not be found. Anyone has an idea on how we could solve this? > > > > Etienne > > > > > > > > > > > > > > > > > > >
