Re: AW: [equinox-dev] Untangling standard and J9 CachingService bundles

[Martin Lippert <lippert@xxxxxxx>]

Hi Heiko,

> Thank you for your help. Now I can build Equinox Aspects again. Yet I am still wondering if I like this design :-)

I understand that, the design of this small piece is not my favorite 
one, too. ;-)

But what I like is that it allows you to install both caching bundles 
(or have both in your launch config) and let them decide which one to 
use depending on the jre they are running on. But maybe this isn't as 
nice as I think...

> Yes, I will enter a bug report. And try to assign it. It's time to get familiar with committer tasks.

Great!

-Martin



> Heiko
>
> -----Ursprüngliche Nachricht-----
> Von: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] Im Auftrag von Martin Lippert
> Gesendet: Donnerstag, 10. April 2008 10:01
> An: Equinox development mailing list
> Betreff: Re: [equinox-dev] Untangling standard and J9 CachingService bundles
>
> Hi Heiko,
>
> 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?
>
> HTH,
> Martin
>
>
> 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
> > Aspects workspace.
> >
> > 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?
> >
> > Heiko
> >
> > _______________________________________________
> > equinox-dev mailing list
> > equinox-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev