Hello Ivo,

To update a bundle, you should not have to stop Amdatu. I know the current 
Cassandra implementation requires that, but it's certainly not going to be the 
official way. That being said, a bundle should be updated by invoking an update 
on it. What you're doing in the second and third steps is basically 
uninstalling bundle X and installing bundle Y. In such cases, the configuration 
will indeed not be bound (and that behaviour is correct). Also, you loose your 
bundle cache.

Probably the best way is to overwrite the existing file, as that is the way 
FileInstall "recognizes that this is an update of an existing bundle". So yes, 
you need to rename your bundles for that, probably eliminating the version 
number in the file name altogether.

Greetings, Marcel


On Feb 7, 2012, at 13:45 PM, Ivo Ladage-van Doorn wrote:

> Hi All,
>  
> Recently this issue has been raised for Amdatu Cassandra;
>  
> http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-153
>  
> The question is how an application build on Amdatu is supposed to be upgraded 
> to a new version (without provisioning, as this is not yet GA). Right now, 
> our bundles contain version numbers (ie 
> org.amdatu.cassandra.application-0.2.2.jar). When you follow these steps just 
> to upgrade this bundle:
> ·         Stop Amdatu
> ·         Remove org.amdatu.cassandra.application-0.2.2.jar from /deploy
> ·         Add org.amdatu.cassandra.application-0.2.3.jar to /deploy
> ·         Start Amdatu
>  
> Then the felix configuration manager will refuse to bind the configuration to 
> this new version of the bundle;
>  
> [2012-02-07 12:42:06] ERROR: Cannot use configuration 
> org.amdatu.core.cassandra.application for 
> [org.osgi.service.cm.ManagedService, id=221, bundle=48]: Configuration bound 
> to bundle file:/D:/Amdatu /deploy/org.amdatu.cassandra.application-0.2.2.jar 
> [org.apache.felix.configadmin]
>  
> And the bundle (and so in this case; the whole application) will fail to 
> start. What should be the plan of action to perform such an upgrade?
>  
> Regards, Ivo
>  
> GX Software | Ivo Ladage-van Doorn | Product Architect | Wijchenseweg 111 | 
> 6538 SW Nijmegen | The Netherlands | T +31(0)24 - 388 82 61 | F +31(0)24 - 
> 388 86 21 | [email protected] | www.gxsoftware.com 
> |twitter.com/GXSoftware
>  
> _______________________________________________
> Amdatu-developers mailing list
> [email protected]
> http://lists.amdatu.org/mailman/listinfo/amdatu-developers

_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers

Reply via email to