|WikiProject Java||(Rated Start-class, Low-importance)|
- 1 explanation in simpler/clearer terms?
- 2 Why a software infobox?
- 3 OSGi Definition
- 4 Comparison / Evaluation
- 5 Evaluation
- 6 Life-cycle needs security info/link
- 7 Needs section on how this is a good example of the Inner-platform effect.
explanation in simpler/clearer terms?
To be quite honest, after reading the introduction, I'm still wondering what OSGi is. It might be nice to cut down on the buzzwords and instead try to explain it in simpler/clearer terms.
- Additionally, the very first sentence is about OSGi Alliance, and not OSGi. The organization behind a specification is of course important, but I am very doubtful to it being that important. TERdON 13:25, 28 May 2007 (UTC)
- Some definitions or additional articles may be required. What is a "service gateway" (IBM seems to use the term "web services gateway")? There is no other article on the subject. Nitwit005 18:26, 14 August 2007 (UTC)
Just a thought: it is mentioned that the OSGi framework enables installing, starting etc without a reboot, this could be made more clear, I assume that you mean that the java process does not need to be restarted in order to install new modules. A reboot seems like a computer reboot, and the link further strengthen the idea. mabac 19:39, 29 Jan 2012 (CET)
- In essence it’s a fine example of the Inner-platform effect. They re-invented the wheel of small programs interacting with each other on a machine, where you can start/stop them, and they connect via ports that are bound to daemons. They just call the machine “JavaVM”, the daemons “modules”, the applications “bundles”, the ports “interfaces”, the coordinating OS “services registry”, etc. Typical enterprisey consultant FAIL. — 18.104.22.168 (talk) 17:41, 4 March 2012 (UTC)
- Interesting - OSGi originated from the embedded world. First do some investigation and understanding before commenting? FAIL. — Preceding unsigned comment added by Pkriens (talk • contribs) 10:59, 17 November 2012 (UTC)
- Judging by the comments here the introduction is clearly not achieving its aim. I would be willing to work on a better version, but it would be good to get feedback (preferably from non-experts) so that I can see whether I'm actually doing any better. Reffik (talk) 20:16, 3 July 2012 (UTC)
Why a software infobox?
OSGi is not a specific piece of software but rather a specification; like J2EE is a specification and WebLogic is an implementation.
In addition to the above comment, I'd like to add my concern for the fact that the infobox states Java as OSGi's operating system, which really doesn't sound right. First of all, OSGi is not bound to a specific operating system, and second, Java is not an operating system. --22.214.171.124 (talk) 09:55, 17 July 2012 (UTC)
- Once you get past all the buzzwords, it seems to be about a standard for hot-pluggable modules, but I'm still not sure ;-) 126.96.36.199 (talk) 21:14, 17 March 2010 (UTC).
- See my section below about the Inner-platform effect. The analogy clarifies it instantly. — 188.8.131.52 (talk) 17:47, 4 March 2012 (UTC)
Comparison / Evaluation
There is now quite a long list of OSGi projects and platforms. It would be a very good time to establish some criteria for how these alternatives compare and relate.
For example; I was looking at getting into a FOSS project that uses Knopflerfish. In this case my purpose is to take part in an open source OSGi based project. I'd like to know, or compare Knopflerfish with one or two other FOSS OSGi alternatives like Felix, Glassfish or Equinox.
There are quite a few good models for comparing and evaluating open source on wikipedia already. I'll add my thoughts on what distinctions I'd look for when comparing something like an OSGi architecture (specification).
Collate each project's feature with the OSGi and other implementation projects. This ought encompass features that are outside the (or, yet to be included) in the OSGi core and for optional OSGi parts.
Compare the interface implementation as well as the effective interchangeableness for bundles between on OSGi implementation and another. I also reckon that this area should include an evaluation for (any?) offered bundle and component repository (e.g. like the Felix repository).
interoperability and flexibility
What development and project tools and frameworks support or interoperate with a particular OSGi model?
Compare the projects themselves on the factual or basic areas like
- affiliates, obligation, etc
The life-cycle says that all life-cycle operations are protected by security, but that text doesn't have a link to a description of the security methodology, and the toplevel article index doesn't have a section about security either. Somebody please update this article to include material and/or link. 184.108.40.206 (talk) 16:56, 28 March 2011 (UTC) Twitter.Com/CalRobert (Robert Maas)
Needs section on how this is a good example of the Inner-platform effect.
They re-invented the wheel of small programs interacting with each other on a machine, using a OS to coordinate everything, where they run/quit, and they communicate via ports/sockets that are bound to daemons/services. They just call the machine “JavaVM”, the daemons “modules”, the applications “bundles”, the ports “interfaces”, the coordinating OS “services registry”, etc. Typical enterprisey consultant FAIL. — 220.127.116.11 (talk) 17:45, 4 March 2012 (UTC)
This needs to be clarified, so people can avoid it.