3 ms·

I do not know of any big OSGi success apart from eclipse. At one point Spring put a lot of effort and then they dump all that at eclipse project after not seein

by geodel 10y ago

I do not know of any big OSGi success apart from eclipse. At one point Spring put a lot of effort and then they dump all that at eclipse project after not seeing much traction. Apache has bunch of OSGi related projects and they do not seem very popular compared to straightforward Java/EE components. For my applications I see some value in Jigsaw specially modular images. Despite being available for long time OSGi still is some esoteric technology without mass developer appeal whereas Jigsaw seems to have potential to be really useful to lots of developers. It is rather sad that OSGi people keep piling on Oracle for not using their barely successful technology.

chopin 10y ago
I worked a good deal with OSGi and think it is sad that it didn't get more traction in the server world. I once adapted a jetty container to use OSGi dependencies instead of packaging all dependencies into a single war file. I gained wonderfully light weight deployment units and the possibility to patch dependencies without touching downstream modules.
- mcguire 10y ago
  I used the SpringSource server (later known as Eclipse Virgo) as a sort of "platform as a service" for enterprise apps. It could deploy anything from plain war files up to OSGi-aware apps that could access custom services for configuration, db access, authentication/authorization, and so forth. Worked rather well, with decent uptime and no hair pulling on my part. The down side was that OSGi requires modularization, which exactly no Java developers to my knowledge had any experience with. Plus OSGi modularity is entirely done at runtime and Spring's tooling to try to support it was incredibly flakey. Conversations went like: "My app works fine on my dev box but blows chunks when I try to deploy it." Me: "You have to be explicit about whay you are depending on in your app's manifest." "I see your lips moving, but all i hear is barks, grunts, and squeals." "Sigh. I'll fix it." I can't really see jigsaw making the situation any better, especially since it explicitly ignores versioning and containers.
  - chopin 10y ago
    On the other hand you have the same kind of problems with Maven. You have to state your dependencies explicitly which can be a pain. And Maven does not support multiple versions when running tests. Everything is lumped into one classloader (afaik), where I sometimes wish Maven would make use of something OSGi like. With regards to dependency declaration both are pretty similar.

by geodel 10y ago

chopin 10y ago

I worked a good deal with OSGi and think it is sad that it didn't get more traction in the server world. I once adapted a jetty container to use OSGi dependencies instead of packaging all dependencies into a single war file. I gained wonderfully light weight deployment units and the possibility to patch dependencies without touching downstream modules.

mcguire 10y ago
I used the SpringSource server (later known as Eclipse Virgo) as a sort of "platform as a service" for enterprise apps. It could deploy anything from plain war files up to OSGi-aware apps that could access custom services for configuration, db access, authentication/authorization, and so forth. Worked rather well, with decent uptime and no hair pulling on my part. The down side was that OSGi requires modularization, which exactly no Java developers to my knowledge had any experience with. Plus OSGi modularity is entirely done at runtime and Spring's tooling to try to support it was incredibly flakey. Conversations went like: "My app works fine on my dev box but blows chunks when I try to deploy it." Me: "You have to be explicit about whay you are depending on in your app's manifest." "I see your lips moving, but all i hear is barks, grunts, and squeals." "Sigh. I'll fix it." I can't really see jigsaw making the situation any better, especially since it explicitly ignores versioning and containers.
- chopin 10y ago
  On the other hand you have the same kind of problems with Maven. You have to state your dependencies explicitly which can be a pain. And Maven does not support multiple versions when running tests. Everything is lumped into one classloader (afaik), where I sometimes wish Maven would make use of something OSGi like. With regards to dependency declaration both are pretty similar.