>________________________________
> De: Richard S. Hall <[email protected]>
>Para: [email protected] 
>Enviado: martes, 29 de mayo de 2012 0:02
>Asunto: Re: OBR RepositoryAdmin content in embeded framework
> 
>On 5/28/12 21:03 , Matias SM wrote:
>> Hi again Richard,
>> I've been investigating further and I realized my confusion came because it 
>> seems that, while OBR takes into account the installed "by hand" bundles to 
>> resolve as requested, it doesn't respond about those resources (associated 
>> to the bundles installed "by hand").
>> That is, if I try to "resolve()" a bundle by using the RepositoryAdmin, it 
>> knows about the installed by hand bundles. But, if I try to "getResources()" 
>> or "discoverResources(..)", I get no results.
>> 
>> Is there a way of getting the installed "by hand" resources from the 
>> RepositoryAdmin without creating a repository?
>
>Off the top of my head, I don't know. I would assume that the RepositoryAdmin 
>is only querying actual repositories for discoverResources() et al, so you 
>won't get back resources from the "fake" local repository.
>
>Not sure what is the correct thing here, but I'm inclined to think the current 
>behavior makes sense, since technically installed bundles do *not* form a 
>repository (e.g., it is not possible to download them).
>


Thank you for the clarifications Richard, I understand your 
point and I agree with you. However, I may be wrong but, bundles (I 
think) are always installed from a source, so it may be possible to use 
that as the URI of the resource.

Related to this, now that you mention it, I think that when creating a 
repository from bundles (by using the API), the resulting xml doesn't 
have a an URI attribute for the resources. Wouldn't that be wrong, 
taking into account that the resources should be downloable?

Kind regards


>-> richard
>
>> Thank you in advance for your help
>> Kind regards
>> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to