Oscar Issues
Preliminary release version: 0.3.0 - March 14, 2001
- As stated elsewhere in the Oscar documentation, Oscar is not 100%
compliant with the OSGi specification yet. Some areas of
non-compliance are simply due to the fact that I haven't gotten
to that point yet, others are due to the fact that the specific
issue may be lower priority for me. Regardless, the goal
for the Oscar as an OSGi framework is 100% compliance with the
framework specification and eventually with the service
specification portions as well. Some specific implementation
issues are mentioned below.
- Update is currently not implemented at all. I had an initial
implementation of update that worked, but some internal changes
made broke it. At this point I am waiting to finalize how I do
bundle caching to finish update; update itself should not be
a problem. This will not affect bundle developers.
- The current approach to bundle caching is going to be changed since
I do not like it very much. This will not affect bundle
developers.
- I have not tried to address security at all in this release. I have
experience in this area from a previous project and I am not expecting
great difficulty, I am just concentrating on functionality first.
- I plan on making some internal changes to the BundleImpl
class so that I can provide "container services" easier. This will
not affect bundle developers.
- It is possible to create a dangling reference to bundles. For
example, assume bundle A depends on bundle B.
If you install B and then uninstall it, and then you try
to install and start A, the framework will incorrectly
believe that B is still loaded. The OSGi specification is
somewhat vague, but I believe that uninstalled bundles must be kept
around if they are in use, but in this case it wasn't in use and
sometimes it is difficult to know the difference. I will investigate
this and come up with a reasonable solution.
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