Hi all, Can we try this out for some well known bundles (covering different types) and see whether it works or not?
For example, what happens if you use this approach to patch the Registry/UM kernel in Carbon 4.2.x? If it works fine, if not, what are the problems that we need to fix? Then, what happens if you use the same approach for a UI bundle? and so on... Thanks, Senaka. On Mon, Jan 20, 2014 at 10:11 PM, Sameera Jayasoma <[email protected]> wrote: > Hi Azeez, > > This is the standard way of updating an OSGi bundle using the command line > console. It is possible to do updates using OSGi APIs. > > I guess we need to re-think about our patching strategy. I mean where to > place patches etc. Because to update an OSGi bundle, AFAIK you simply have > to replace the existing bundle with the new bundle in the filesystem and > invoke the update call. > > This is also related to dynamic bundle loading. So I think we need to > design our hot deployment bundle and the patching strategy properly first. > > Thanks, > Sameera. > > > On Mon, Jan 20, 2014 at 6:12 AM, Afkham Azeez <[email protected]> wrote: > >> Folks, >> Our patching strategy has been to make an exact copy of the patched jar, >> and then during startup, do a bundle replacement. >> >> With Carbon 5, our aim is to be able to patch bundles without requiring a >> full restart of the OSGi runtime. I read somewhere that; >> >> >> >> update <bundle id> file:patches/<new Bundle name> >> >> >> is one way of patching a bundle. >> >> So say we are patching org.wso2.carbon.core-4.2.0.jar, we could have a >> patched jar called org.wso2.carbon.core-4.2.0.p0001.jar and then do; >> >> >> >> update 23 file:patches/p0001/org.wso2.carbon.core-4.2.0.p0001.jar >> >> >> >> Will this strategy work? >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>* >> *email: **[email protected]* <[email protected]> >> * cell: +94 77 3320919 <%2B94%2077%203320919> blog: * >> *http://blog.afkham.org* <http://blog.afkham.org> >> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * linked-in: **http://lk.linkedin.com/in/afkhamazeez >> <http://lk.linkedin.com/in/afkhamazeez>* >> >> *Lean . Enterprise . Middleware* >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Sameera Jayasoma, > Architect, > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://sameera.adahas.org > twitter: https://twitter.com/sameerajayasoma > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections > Mobile: 0094776364456 > > > Lean . Enterprise . Middleware > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
