[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Untangling standard and J9 CachingService bundles
- From: Martin Lippert <lippert@xxxxxxx>
- Date: Thu, 10 Apr 2008 10:01:19 +0200
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 220.127.116.11 (Windows/20080213)
to let you setup and even build equinox aspects including the J9 caching
service you can import the project "build.ibm.oti". This mocks all the
shared classes API that is used for your workspace.
And the dependency on J9 in the standard caching feature is optional, I
think, so you don't need a J9 for running equinox aspects with the
standard caching service.
I agree to your comment with regards to the dynamics of the caching
services. Would you enter a bug report for this?
Heiko Seeberger wrote:
Hi Martin and Equinox Aspects fans,
In the current release of Equinox Aspects the standard caching service
(bundle org.aspectj.osgi.service.caching) depends on the IBM J9 VM
(import com.ibm.oti.shared.Shared). That makes it impossible for anyone
without an IBM J9 VM installed (e.g. me) to set up a working Equinox
What do you think about the following solution?
1. Remove the dependeny:
This is easy to do (remove Activator.shouldRegister()).
Consequence: Now we might have both CachingServices registered.
2. Use service.ranking to let the IBM J9 CachingService be used in case
of both registered.
In the Activators of the both bundles we use services properties and
give the J9 CachingService a higher service.ranking.
On the long run we also should think about service dynamics: What if
someone stops the bundles providing the used CachingService?
equinox-dev mailing list