Oscar Issues
Release version: 1.0.4 - February 18, 2005
- Oscar is not 100% compliant with the OSGi specification yet, but it
is very close. There are likely some fine-grained
areas where Oscar differs from the behavior described in the
specification. The goal is to eliminate these difference, so please
voice you concern over any divergences that you discover.
- Current support for native libraries is not 100% compliant with the
OSGi specification; the specification says that the framework should
error if a specified native library does not exist for the platform
on which the bundle is being installed. From my point of view, this
is too restrictive since it may actually be the case that you need
a native library on one platform, but not on another; the OSGi
specification apparently does not allow this situation but Oscar does.
This may change or become a configurable "Oscar extension" in the
future.
- Also in native library support, it appears that operating system and
platform variables are not always consistent on all JVM implementations.
I have just hardcoded some values from my machines and tried to guess
reasonably for other values. As a result, Oscar may not recognize
some platforms. Perhaps these values should be placed in a config
file or something.
I am sure that I have missed some issues, so feel freel to contact me
at heavy@ungoverned.org if you have
any problems.
Richard S. Hall