I see - It's in an IllegalState until you refresh
On 25/01/2008, Mark [EMAIL PROTECTED] wrote:
Try adding:
Import-Package: bundlea.service
to the Bundle A manifest.
=
I just tried the suggestion above - but it blows up?
Framework
Try adding:
Import-Package: bundlea.service
to the Bundle A manifest.
=
I just tried the suggestion above - but it blows up?
Framework is launched.
idState Bundle
0ACTIVE org.eclipse.osgi_3.3.1.R33x_v20070828
1
Mark,
Since your service interface (IA.java) is contained within bundleA,
bundleB requires a package import from bundleA. The effect that
you're seeing is that the old version of bundleA remains in the system
and is still used by bundleB after you call update. Therefore you
now have two
Date: 01/25/2008 02:43 PM
Subject:Re: [equinox-dev] is this a service tracker bug
and CTO of the OSGi Alliance
[EMAIL PROTECTED]
office: +1 386 848 1781
mobile: +1 386 848 3788
From:
Mark [EMAIL PROTECTED]
To:
Equinox development mailing list equinox-dev@eclipse.org
Date:
2008-01-25 13:06
Subject:
Re: [equinox-dev] is this a service tracker bug?
I see - It's
386 848 3788
From:
Mark [EMAIL PROTECTED]
To:
Equinox development mailing list equinox-dev@eclipse.org
Date:
2008-01-25 12:59
Subject:
Re: [equinox-dev] is this a service tracker bug?
Try adding:
Import-Package: bundlea.service
to the Bundle A manifest
Thanks.
So that's expected behaviour - and all makes sense.
Regards
Mark
On 25/01/2008, Jeremy Volkman [EMAIL PROTECTED] wrote:
Mark,
Since your service interface (IA.java) is contained within bundleA,
bundleB requires a package import from bundleA. The effect that
you're seeing is that
Try adding:
Import-Package: bundlea.service
to the Bundle A manifest.
Then when bundle A is updated to A',
A' will import the package from A which is where bundle B is importing
it. So bundle B can see the service from A' since it implements
the interface from A. (This follows from Tom
Mark,
This is because of the pending removal of the old class loader from bundle
A which bundle B is still wired to for package bundlea.service. You do not
see the new service from bundle B because you would get a
ClassCastException. The Framework filters out services that it knows you
do not
Which is the prime reason why you should also import your service
package in A, so that it can wire to other providers if they are available.
- richard
Jeremy Volkman wrote:
Mark,
Since your service interface (IA.java) is contained within bundleA,
bundleB requires a package import from
Date: 01/25/2008 12:10 PM
Subject:Re: [equinox-dev] is this a service tracker bug
11 matches
Mail list logo
