Comments on: Diagnosing OSGi uses conflicts

By: Jeshurun

Jeshurun — Sun, 13 Nov 2011 07:40:26 +0000

Thanks, this was very useful. It is less than a week since I started working with Spring dm and Osgi and its blogs like this that have helped me come a long way in this short span of time. Thanks again, much appreciated.

By: 5 little things I want from a build | Java Ekspert Danmark

5 little things I want from a build | Java Ekspert Danmark — Wed, 28 Sep 2011 20:07:15 +0000

[...] Software today face increasingly reuse. Especially with runtime models such as OSGi, it is vital that we modularize into smaller and more dedicated units. This sooner rather than later starts to provide you with a lot of dependency graphs, that essentially needs to be resolved. Now, I don't really care how it is specified, but the point being, that some software knows and publish their dependency requirements, and as such we can use automated dependency management, actually we should. Why have to do this stuff manually?? Maven dependencies was the first. Good or bad, they were there and with the right metadata in your poms, it actually gives you full dependency management. However, over the years I have become increasingly disappointed with the quality of the provided software (as in the examples here). It is also emerging in OSGi applications to have this full dependency resolution, however, there are quite a few catches in there as well. [...]

By: “Uses” Directive In OSGi « rossenstoyanchev.org Blog

“Uses” Directive In OSGi « rossenstoyanchev.org Blog — Sun, 15 Nov 2009 21:56:15 +0000

[...] follow-up blog by Rob Harrop that provides a realistic example involving Spring ORM and two versions of [...]

By: Ahmed Adel

Ahmed Adel — Tue, 20 Oct 2009 10:04:22 +0000

Unable to start eclipse Equinox

when i am tryig to start the equinox using :-
equinox% java -jar org.eclipse.osgi_3.4.0.v20080605-1900.jar

i found error log like the following:-

!SESSION 2009-10-20 11:25:40.421 ———————————————–
eclipse.buildId=unknown
java.version=1.6.0_15
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ar_EG

!ENTRY org.eclipse.osgi 4 0 2009-10-20 11:25:41.015
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at org.eclipse.core.runtime.adaptor.EclipseStarter.main(EclipseStarter.java:150)

i dun know what to do and i searched the internet for a solution but failed to find anything.

i appriciate if you can help me

Kindly
Ahmed Adel

By: Colin Sampaleanu

Colin Sampaleanu — Tue, 25 Nov 2008 19:25:39 +0000

William,

I think you are missing the point that this is shifting the level of complexity (reducing it significantly), and allowing you to resolve versioning/depending issues upfront. This is turning a versioning/dependency issue (when it happens) from something that can introduce significant cost and risk, and is often nasty enough to make you want to bash your head into a wall in frustration, to something that a regular person can solve.

I have lived through real DLL hell in both C/C (under Windows) and Java (conflicting class libraries, or JBoss universal classloader from hell that decided to break at random times when something changed), and I do not want to go there again…

Colin

By: William Louth

William Louth — Tue, 25 Nov 2008 19:01:02 +0000

Looks more like it is basically shifting the complexity from one user/role/stage to another. It amazes me how many people get diagnosed with ADD when viewing such blogs……

William

By: Rob Harrop

Rob Harrop — Sun, 23 Nov 2008 22:43:34 +0000

@Sebastian

In fact uses and other OSGi constraints are intended to prevent DLL hell-style problems. Specifically, uses prevents spurious ClassCastExceptions from happening at runtime – the kind like 'Cannot cast Foo to Foo'. Uses gives you a static check to make sure the class space is consistent, and indeed gives the constraint resolver the chance to create class spaces that are consistent.

Rob

By: Rob Harrop

Rob Harrop — Sun, 23 Nov 2008 22:41:00 +0000

@keesun

Well spotted – I've corrected this now.

Regards,

Rob

By: Sebastian

Sebastian — Sun, 23 Nov 2008 21:26:26 +0000

Looks like DLL-Hell

By: keesun

keesun — Sun, 23 Nov 2008 08:29:10 +0000

I think, there is a misspell on the first examples's explanation.

"Clearly, only the eclipselink_2 bundle can satisfy this constraint."

"eclipselink_2" should be "eclipselink_1".

doesn't it? ^^;