Determine impact of class loading behaviour re: configuration bundles

Type: Bug
Status: Closed
Priority: 2 Major
Resolution: Fixed
Component/s: X-Common Code
Labels:

Assignee: nharward
Reporter: nharward
Created: January 15, 2007
Votes: 0
Watchers: 0
Updated:
July 27, 2012
Resolved:
January 24, 2007

Description

Configuration bundles will require an additional class loading layer to be injected into the DSO client runtime as they are dynamic; this issue is to track the potential problems and issues regarding this. Currently there is no implementation, but Equinox and Knopflerfish are leading contenders in this area as OSGi implementations, we might or might not roll our own as well.

Comments

Nathaniel Harward 2007-01-24

This does not really appear to be an issue (we have chosen Knopflerfish as our implementation) – the OSGi framework stipulates very strict and very isolated class loading rules for a bundle, and we have configured Knopflerfish to delegate unknown classes to the same loader that any other DSO client code would use. As we are not explicitly exporting any com.tc packages into the OSGi framework, this delegation is necessary but again, does not appear to cause any problems or behave in unexpected ways.