Jacek Laskowski schrieb:
> Move them to a profile and let them be "provided".
>
Can you send some references. Don't really know what you mean.
Keep in mind, that some modules will make heavy usage of the
dependencies (Resolving bundles, finding services).
And even in the classic usage scenario, at least the following code
would be needed (As far as I know)
If (context != null ) {
// do some OSGI stuff
} else {
// do it the classic way
}
> You can specify optional dependencies in MANIFEST.MF. They don't have
> to be available upon bundle startup and delivered later on.
>
Now I'm completely in the dark. How is could I possibly implement the
following scenario
bundle1: openejb-client
bundle2: my-client
bundle3: my-entity-classes
Each bundle has its one class-loader, not seeing the classes of the
other. How can I foresee this scenario and how to supply
class-loading information via the OSGi-Manifest (I only know the Eclipse
way via Bundle-Policies, which is actually the way I'm doing this)
-
Olli
