[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Registry cache behaviour when no cache exists in both primary and shared configuration locs


This sounds like bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=139690 which should be fixed in 3.3.  What version of the Registry are you using?

Tom





Danail Nachev <d_nachev@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

05/28/2007 11:07 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
[equinox-dev] Registry cache behaviour when no cache exists in both primary and shared configuration locs





Hi,

Currently the Registry has the following behaviour implemented in the
ExtensionRegistry.checkCache() method:

1. it checks whether there is a cache info in the primary configuration dir
2. if it fails, it checks if there is a cache info in the shared
configuration dir
3. if this fails too, the shared configuration dir is left as a cache
info destination

This behavior has the side-effect that cache info will be never created,
because shared configuration location is always read-only for the
registry cache. Is such behavior intended?

I'm not very familiar with the Equinox deployment in shared install
scenarios, so it is up to you to decide whether this behavior is a bug
or it is a feature.

--
Danail Nachev
Software Engineer/Development Tools
ProSyst Labs EOOD
-------------------------------------------------
stay in touch with your product.
-------------------------------------------------
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev