Release Notes Knopflerfish 6.1.0 (OSGi R6)
Maintenance release of Knopflerfish 6 available from http://www.knopflerfish.org/releases/6.1.0. Released 2017-02-08.
Knopflerfish 6 is an implementation of the "OSGi Service Platform Release 6". It contains all services specified in the "Core Specification" and most of the non Enterprise Edition related services specified in the "Compendium Specification".
The Release Notes include all new features & changes for Knopflerfish 6.1.0 compared to the release of Knopflerfish 6.0.0
Knopflerfish Framework - OSGi Core Specification
Fixed issue #7. Always allow start of read-only unpacked bundles.
Fixed issue #11. Do not try to override framework internal export package resources with matching files from current directory. To override, use framework property org.knopflerfish.framework.system.packages.file
Fixed issue #8. Could not start on Java 9 because of new version schema.
Set default value for framework property org.knopflerfish.framework.is_doublechecked_locking_safe to TRUE for all instances since we don't run on Java 1.4 anymore.
OSGi Compendium Specification
Fixed issue #17, NPE in Component.newComponentConfiguration when multiple component instances are bound to the same service and have the same target propertymultiple Declarative Services component instances are not created for multiple factory configurations.
Fixed NPE, that occured if you inspected a component with CM config that had been disabled.
Fixed problem with components not getting factory configuration data present before activation.
Fixed problem with component deactivation method not getting factory configuration properties if multiple factory configuration instances were registered.
Fixed issue #14, StackOverflowError when using JAXRS publisher. Removed a faulty re-register of service during deactivation of a delayed component configuration.
Fixed missing reference DTOs for ServiceComponentRuntime.getComponentConfigurationDTOs.
Fixed issue #10. ServletResponse.setContentType(null) now resets the content type to default values. This is the same behaviour as jetty.
ServletResponse.getContentType() is changed to only append the charset if it has been set explicitly. This is the correct behavior according to the Servlet API Documentation.
Fixed issue #18. The HTTP server error pages could get an incorrect page encoding.