Class Not Found when connect

[moquette-io]

Class Not Found when connect

[PaoloFi]

I solved the problem . At compile time I had to add this to the pom:

sonatype-snapshots https://oss.sonatype.org/content/repositories/snapshots

because I could not download the jar relative to MapDb .So I haven't downloaded the file org.mapb.mapdb.1.1.0 fixed .

Fix:
add DynamicImport -Package : * in the manifest file of the jar org.mapb.mapdb.1.1.0

[andsel]

I reopen the issue because the fix to MapDB was already proposed to the MapDB team and they replied that's not the correct solution [https://github.com/jankotek/mapdb/pull/377]. I'll fix once I could study better the OSGi

[maggu2810]

Any news?

[maggu2810]

The ESH project uses mapdb in an OSGi context.
Perhaps this could help you: https://github.com/eclipse/smarthome/blob/master/bundles/storage/org.eclipse.smarthome.storage.mapdb/src/main/java/org/eclipse/smarthome/storage/mapdb/MapDbStorage.java

[andsel]

Hi @maggu2810 no news on this, thank you for the link.
I'm truing to embed the MapDB bundle but at moment I'm fighting with strange import error about sun.misc package that can't be importer.

[maggu2810]

IMHO add MapDB to the OSGi bundle of moquette is also just a workaround. If we have multiple bundles in our OSGi runtime (the normal use case) I would just include one MapDB bundle. If multiple bundles ship with embedded MapDB classes, this is not the intention of OSGi (but this is just my understanding of the OSGi framework).

[andsel]

I've dropped the support for OSGi in version 0.7. Because I think that nobody use it in OSGi environment and I'm not confident with OSGi. I wasn't able to fix the pax-runner configuration and drain dev resources to keep OSGi compatibility that's not usefull to anybody I suppose, at the end Moquette could be embedded by other OSGi project just wrapping it.

[kaikreuzer]

@andsel From my pov, this is an unfortunate decision - as you might remember, I was actually still planning to integrate Moquette into openHAB as I think this is a great fit. Also @maggu2810 uses OSGi with MQTT and many others do as well (see e.g. @andypiper at https://gist.github.com/andypiper/9654252). Since MQTT is very strong at Eclipse and so is OSGi, I think this is a very relevant combination.

[andsel]

Hi Kai,
the motivation for the decision is that I'm not a geek in managing OSGi,
and OSGi is not such a simple thing to manage correctly, every bug or error
notification related to the OSGi compatibility in Moquette, taken me a lot
of time end effort, so waiting better times (when I can manage correctly an
OSGi environment or somebody with better skills on this stuff jump into
project) I decided to concentrate on bugfixes and features, but if you or
somebodyelse with competence in OSGi want to contribute with a patch
regarding that stuff, it really welcome.

Andrea

On Mon, Nov 2, 2015 at 12:06 PM, Kai Kreuzer [email protected]
wrote:

@andsel https://github.com/andsel From my pov, this is an unfortunate
decision - as you might remember, I was actually still planning to
integrate Moquette into openHAB as I think this is a great fit. Also
@maggu2810 https://github.com/maggu2810 uses OSGi with MQTT and many
others do as well (see e.g. @andypiper https://github.com/andypiper at
https://gist.github.com/andypiper/9654252). Since MQTT is very strong at
Eclipse and so is OSGi, I think this is a very relevant combination.

—
Reply to this email directly or view it on GitHub
https://github.com/andsel/moquette/issues/14#issuecomment-152989443.

[kaikreuzer]

@andsel If there is no general problem with having the OSGi bundle built, I would prefer if you could leave it in - if there are bug reports like this, which you cannot easily solve, just leave them open and wait for some one with OSGi knowledge to come up with a PR with a fix. But dropping the bundle from the build does not even give people the chance to fix it.

[andsel]

Hi @kaikreuzer @maggu2810 @PaoloFi, to track this feature request I've created a new issue, #122

[doandzhi]

Hello! This issue is almost 3 years old and I still don't seem to find a possible solution for it. Can anyone give me an advice and/or possible solution of this ClassNotFoundException of the internal class QOSType.

[andsel]

Given the fact that managing OSGi is not trivial, and I dont' want to spend time in fixing OSGi deps, I dropped the support for OSGi in Moquette and closed this issue as not anymore valid.
Andrea