Issue #257: Better OSGI Compability

We are currently using objectdb using osgi. However, the objectdb jar seems to be very monolithic and should be more modular to make it easier to use it with osgi, samples are:

- Remove SWING dependency from core objectdb bundle

- Externalize persistence and jdo apis and not putting them into objectdb jar (conflicts with glassfish jars otherwise)

- Build objectdb as ready-made osgi jar bundle (We're doing this currently)

- Provide possibility to use classes through different bundles with the objectdb bundle requiring to import all other packages for correct functionality (which is due the special osgi class loader strategies)

Making ObjectDB more OSGI friendly is an important feature request.

The one JAR packing was intended to simplify deployment, but apparently in some cases it does cause problems.

Could you please provide more details on the last two points (including instructions and examples)?

Build 2.3.3_03 includes initial OSGi support.

The objectdb.jar is created now as an OSGi bundle and may be used from other OSGi bundles.

Eclipse plugin specific issues and suggestions should be discussed in another thread.

General OSGi issues and suggestions should be discussed here.