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)