Could really use this being an OSGi bundle. [moved]
See original GitHub issueThis is Issue 405 moved from a Google Code project. Added by 2012-04-26T10:29:10.000Z by JamiePBo…@gmail.com. Please review that bug for more context and additional comments, but update this bug.
Original labels: Type-Defect, Priority-Low
Original description
<b>What version are you using? (Morphia/Driver/MongoDB)</b>
v 1.00-SNAPSHOT of Morphia.
This is a feature request really. I'm trying to use morphia with the Mongo OSGi bundle and it's making things really tricky. - Company going of the idea of using Morphia as a result.
Personally I'm loving morphia and really want to get it working in an OSGi environment. - tks.
Issue Analytics
- State:
- Created 10 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Chapter 6. Moving toward bundles - OSGi in Action
The common choice is to use the bundle version, which implies that the packages change at the same rate as the bundle, but...
Read more >Unraveling Java and OSGi class loader problems
Thus OSGi becomes a web of bundle class loaders that delegate to each other. If a class is not on your bundle's class...
Read more >Why does it appear that OSGi-classloading is being bypassed?
It's possible that the library is using the Thread Context ClassLoader (TCCL ). If the bar package is visible to your own bundle...
Read more >Creating OSGi bundles - Spring
Most of the time used on OSGi metadata is likely to be spent on Export/Import package entries as they describe the relationship between...
Read more >OSGi on the Server Side - Web Forefront
The Java packaging bundle: Of course no environment or framework is exempt from having its own packaging model, so just as you may...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Given the age and niche interest in this, I’m going to close this. Between testing and maintenance costs, I’m not seeing the value especially when things like Java 9 modularity are more pressing. If there’s actually active interest, this can be revisited.
Hello,
is this issue still alive? I wanted to report the same issue as the comment above from gbivins, but with a different container. I tried it with Liferay: