Hi,
Richard S. Hall schrieb:
I think you are correct, it currently does not allow you to control the
order in which it searches the repositories. This is a general issue and
is somewhat complicated to handle in a generic way. Another similar
issue is that if two or more repositories offer the same bundles or
bundles that offer the same needed capabilities, how to know from which
repository to choose. If you strictly have an ordered set, then it might
be possible to deal with it, but in the general case it is difficult.
I completely agree. Why not change the RepositoryAdminImpl as proposed
by Krishanu. This would at least give a somewhat easier user experience
in that the user might just get the repositories back in the order of
calling the add method (mostly though because referrals may add
additional repositories, which might interfere, but I think this is a
minor issue here).
WDYT ?
Regards
Felix
-> richard
Krishanu wrote:
Thanks a ton Richard. Following your algorithm, I could achieve
exactly what I was looking for.
The only thing I find a little finicky, is that, we can not specify a
sequence in which the repositories needs to get searched( correct me
if I am
wrong) for the bundle resolving to happen. To achieve that, I had to
modify
the felix OBR source code. I changed the map definition in
RepositoryAdminImpl class to "private Map m_repoMap = new
LinkedHashMap();"
from simple hashmap. Please suggest if there is a better way to do it.
Just to reiterate my requirement, I need to resolve the bundle from my
local
repository(if it is already there), and then look into the remote
repositories in the specified order.
->krish
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
