
A Twitter channel for your daily news about the OSGi framework, ecosystem and community. Managed by @SanfteSchorle
World
Joined February 2019
- Tweets2.8K
- Following2
- Followers444
- Likes2.7K
OSGi News retweeted
🚀🎉 OSGi.fx v2.4.1 has just been released with new features and bug fixes 🤩
‼️ You can now manage remote OSGi runtimes over MQTT as well 🌐
Download from osgifx.com
Release Notes: github.com/amitjoy/osgifx/re…
#OSGi @OSGiWG @Bndtools @NewsOsgi @OSGiUsers @osgi_vug
OSGi News retweeted
Lost is wrong word, but under-appreciated is right word. Not many appreciate what OSGi can do and hence not widely adopted but still its alive due to all those who appreciates it’s fundamental advantages.
OSGi News retweeted
Learn how to resolve complex OSGi application problems with our guide to the Apache Felix Search Web Console Plugin: https://teapawt.net/t.co/squC7PrVqp
OSGi News retweeted
Replying to @derekm00r3 @gunnarmorling
OSGi News retweeted
Replying to @gunnarmorling
I really miss OSGi’s dependency management, but even OSGi lacks some kind of packages lock file like npm has (when depending on version ranges, you want reproducible builds). Even then, you have very important dependencies like Netty or gRPC that don’t follow semantic versioning.
OSGi News retweeted
Yet you still need the intranet network to make the network calls. This is not a feasible option.
Again, with OSGi, back being locked down to the Java ecosystem, for example, is a restriction, not an improvement.
My point is WASM has the potential to break down -
OSGi News retweeted
You can run microservice based plugins also without Internet, just install them somewhere in Intranet.
I've experiences in OSGi for in-process plugins, and I have to say: very good idea for in-proc plugins, but at the end, out-of-proc plugins rule because a lot of points...
OSGi News retweeted
🚀🎉 OSGi.fx v2.3.1 just got released with new features and bug fixes 🤩
Download from osgifx.com
Release Notes: github.com/amitjoy/osgifx/re…
#OSGi @OSGiWG @Bndtools @NewsOsgi @OSGiUsers @osgi_vug
OSGi News retweeted
Replying to @kelseyhightower
an evolution of the JVM / CLR. prior to the jvm we were downloading and link obj-c code on the fly ... but it wan't "safe".
Taking the JVM, then layering things like Jini, OSGI, etc. for runtime download and execution.
wasm seems like the next step to me
OSGi News retweeted
#SLF4J 2.0.7 has been released fixing OSGi MANIFEST related issues. Many thanks to @HannesWell for his previous assitance in resolving these.
See slf4j.org/news.html for details
OSGi News retweeted
Replying to @kelseyhightower @_exterm
After using Java's OSGi framework for many years, I think the term modulith is fitting.
OSGi News retweeted
Don't want to brag here, but what Google attempts to do with "Service Weaver" I've been doing for over a decade now with OSP (an OSGi-inspired framework for C++) + an RPC framework that transparently falls back to normal function calls if client and server are in same process.
OSGi News retweeted
This looks super interesting! For the OG Java folks like myself, does this remind you a little of OSGi?
This Post is from an account that no longer exists. Learn more
OSGi News retweeted
As @danielbryantuk mentioned, @kelseyhightower this looks like a #GO implementation of #OSGI.
Several mature frameworks #ApacheSling #ApacheFelix implement this concept using @java, used by CMS platforms like @Adobe's Experience Manager.
-this may help Service Weaver community.
This Post is from an account that no longer exists. Learn more
OSGi News retweeted
Replying to @kelseyhightower
Makes me think about OSGi Remote Services. That make me curious how local vs remote method invocation works. Particularly about performances (latency) and error handling (a method I thought was local could return a "ConnectionError" because it was remote and wasn't able to join)
OSGi News retweeted
In OSGi this style of annotation driven exports and automatically created imports work extremely well. I see no reason why it should not work for modules.
OSGi News retweeted
Does it, though? I hear from OSGi users that with all tools in play, the bundle info is barely ever looked at, comparable to imports at the top of a source file. I think that's a huge lost opportunity to deliberately evolve and review a module/bundle.
teapawt.net/nipafx/status/13363461…
Replying to @nipafx
6. Having an auto-generated declaration makes it much less likely that you benefit from one of the biggest benefits of modules: Using a single-source-file description of your entire (sub)project.
medium.com/97-things/take-ca…


















