When camel-cache is configured to use disk storage and an application (OSGi bundle) reads a stored object from this cache, the object is loaded with the wrong class loader, and therefore when it is cast from Object to its class in an application, a ClassCastException occurs.

This *only* occurs when the OSGi bundle has been updated or restarted - i.e. when there are multiple revisions of it. The class loader of the object is the class loader of the first revision of the bundle, while it is expected that the class loader of the current bundle will be used.