Hi Azeez, I have used the said method of updating a bundle, and it worked for me sometimes. But there can be issues when doing this. One issue I have faced is that, if a bundle contained an admin service, then that service gets re-added during a bundle update. Then, Axis2 started complaining two services cannot have the same name.
The said issue won't be there in C5 since we will not be using axis2 based admin services. But there can be other issues like this when the initialization logic happens inside the service component. IMO it's better to do a restart of the server for bundle updates. Thanks, KasunG On Mon, Jan 20, 2014 at 7:42 PM, Afkham Azeez <az...@wso2.com> 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: **az...@wso2.com* <az...@wso2.com> > * 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 > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
