(2010-08-19) * support for Hibernate Core 3.6, Hibernate Validator 4.1, EclipseLink 2.1, EHCache 2.2 * OSGi manifest version range accepts EHCache 2.x as well * added "contentLength()" method to Resource translation to error views as well * mvc:annotation-driven reliably detects JSR-303 and JAXB2 in an OSGi environment * revised @MVC handler method resolution with respect to handler methods on generic interfaces includes #### Changes in version 3.0.2 (2010-04-02) $ ^{*} $ fixed cross-module version ranges in OSGi manifests * fixed contents of org.springframework.web.struts jar * upgraded to Hibernate Validator

version 3.1.2 (2012-07-09) $ ^{*} $ removed INDEX.LIST entries from Spring jar META-INF dir * fixed OSGi metadata for optional "java.inject" package import * fixed AbstractResource'sInputStream-based resource type does not have a filename * Resource "contentLength()" implementations work with OSGi bundle resources and JBoss VFS resources * PathMatchingResourcePatternResolver preserves caching across * added String constants to MediaType Changes in version 3.1 RC2 (2011-11-28) * fixed OSGi manifest for spring-web bundle to not require Apache HttpComponents anymore $ ^{*} $ fixed GenericTypeResolver

is a OSGi-based runtime which provides a lightweight container onto which various components and applications can be deployed. Apache Karaf uses either Apache Felix Framework or Eclipse Equinox OSGi frameworks instances of Apache Karaf can be managed directly from a main instance (root). - OSGi frameworks: Apache Karaf is not tight to one OSGi framework. By default, Apache Karaf runs with Apache Felix Framework, but feature:install camel-spring karaf@root()> bundle:install -s mvn:org.apache.camel/ camel-example-osgi/2.10.1 The example installed is using Camel to start a timer every 2 seconds and output a message

service 6.1. OBR metadata access 6.2. OSGi bundles access 7. Administration ## Overview Apache Karaf Cave is an Apache Karaf sub-project. It provides an OSGi Bundle Repository (OBR) and Karaf Features allows you to directly register a Cave repository into an OBR RepositoryAdmin OSGi service. • Artifact Upload: Users can upload OSGi bundle in a Cave repository. It supports URLs like mvn:groupId/artifactId/version get artifacts present on an "external" repository (local file: or remote http:), looking for OSGi bundles, and copy the artifacts in the Cave repository storage. The cave-server feature provides

Handler 4.9.2. Maven configuration commands 4.10. Provisioning 4.10.1. Application 4.10.2. OSGi 4.10.3. Feature and resolver 4.10.4. Features repositories 4.10.5. Boot features 4.10.6. Features Guide 5.1. Developer commands 5.1.1. Dump 5.1.2. Diagnostic 5.1.3. Dynamic import 5.1.4. OSGi framework 5.1.5. Stack traces printout 5.1.6. Bundle tree 5.1.7. Watch 5.2. Scripting 5.2 5.9.1. Add extended information to bundles 5.9.2. Wiki Syntax 5.10. Creating bundles for non OSGi third party dependencies 5.10.1. Dynamically wrapping jars 5.10.2. Statically bundling jars

transaction framework. Spring 2.5 ships its framework jars as OSGi-compliant bundles out of the box. This facilitates use of Spring in OSGi environments, not requiring custom packaging anymore. ######

multiple includes #### Changes in version 3.0.2 (2010-04-02) * fixed cross-module version ranges in OSGi manifests * fixed contents of org.springframework.web.struts.jar * upgraded to Hibernate Validator TestNG 5.9, and EasyMock 2.5.1 * updated all Spring Framework OSGI manifests to list unversioned imports explicitly * relaxed several OSGi bundle dependencies (optional, extended version ranges) * revised in case of custom BeanInfo * GenericTypeResolver's type variable cache uses weak values (for OSGi compatibility) * fixed CachingMapDecorator to support garbage-collected weak references (again)

installation of the decanter-collector-log feature is enough. The Decanter log collector is using osgi:DecanterLogCollectorAppender appender. In order to work, your Apache Karaf Pax Logging configuration rootLogger = DEBUG, out, osgi:* If you want, you can explicitly specify the DecanterLogCollectorAppender appender: log4j.rootLogger = DEBUG, out, osgi:DecanterLogCollectorAppender, osgi:VmLogAppender ##### feature:install decanter-collector-eventadmin By default, the eventadmin collector is listening for all OSGi framework and Karaf internal events. You can specify additional events to trap by providing a 'etc/org

installation of the decanter-collector-log feature is enough. The Decanter log collector is using osgi:DecanterLogCollectorAppender appender. In order to work, your Apache Karaf Pax Logging configuration rootLogger = DEBUG, out, osgi:* If you want, you can explicitly specify the DecanterLogCollectorAppender appender: log4j.rootLogger = DEBUG, out, osgi:DecanterLogCollectorAppender, osgi:VmLogAppender ##### feature:install decanter-collector-eventadmin By default, the eventadmin collector is listening for all OSGi framework and Karaf internal events. You can specify additional events to trap by providing a 'etc/org

8.3. Deploying bundles using the cluster OBR 9. OSGi Event Broadcasting support (eventadmin) 9.1. Enable OSGi Event Broadcasting support 9.2. OSGi Event Broadcast in action 10. HTTP Balancer 10 supports synchronization of OSGi EventAdmin, OBR (URLs and bundles). The second goal is to provide a Distributed OSGi runtime. It means that using Cellar, you are able to call an OSGi service located on a remote features Optionally, you can install additional features. The cellar-event feature adds support of OSGi EventAdmin on the cluster: karaf@root()> feature:install cellar-event The cellar-obr feature