Hi Azeez, Sameera, Senaka,
In PoC, I could able to get the bundle dependency closure( Bundle which
import packages from updated bundle) of updated bundle and refresh it
pragmatically. This will solve wiring issue with hot update. According to
the offline dicussion had with Senaka, we need to chec
With regards to patches including config file changes, we should make it
possible to hot update config files. Stratos folks are doing this
(somewhat) successfully. The partitions, autoscaling policy etc. are hot
updated.
On Tue, Jan 21, 2014 at 7:52 AM, Afkham Azeez wrote:
> Yes, you have to re
With C5, our dependency on Axis2 will be minimal.
Azeez
On Mon, Jan 20, 2014 at 7:59 PM, Kasun Gajasinghe wrote:
> 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 b
Yes, you have to refresh the dependent bundles. I think we can write our
patching logic to figure out the OSGi wiring (using OSGi WireAdmin) and
then refresh the dependent bundles.
On Mon, Jan 20, 2014 at 11:18 PM, Shameera Rathnayaka wrote:
> Hi Azeez,
>
> As we know in OSGi world we have tow t
Hi Azeez,
As we know in OSGi world we have tow types of dependencies 1) OSGi
services, 2) Bundle wiring . updating a bundle with new bundle we can solve
OSGi services dependencies correctly but when we come to bundle wiring we
need to find out correct dependency closure and refresh that OSGi bundl
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 h
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 replac
On Mon, Jan 20, 2014 at 7:59 PM, Kasun Gajasinghe wrote:
> 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
>
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
s
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 file:patches/
is one way o
10 matches
Mail list logo
