I've created a new thread because people may miss the discussion by
looking at the subject.
Alin Dreghiciu wrote:
> obr://<bundle-symbolic-name> will not suffice I think to trace back
to the
> same resource. You should have at least also the version if you are
working
> with just one repository and if not you should have also the
repository url.
> so a complete url to unique identify the bundle will be something like:
>
> obr://<bundle-symbolic-name>/<bundle-version</<repository-url>
>
> And as I suppose the bundle was intalled in the first place by bundle
> repository service it could be changed to make an url in more generic
form
> as for example:
>
obr://<repository-url>?(&(name=<bundle-simbolic-name>)(version=<bundle-version>))
>
> where the query (part after ?) could be any obr supported query, but
in the
> case above it will determine unique the bundle.
>
>
> Couldn't then be made generic?
It's not the clement project which needs to be changed for you request,
but the "bundlerepository" project (Look at
RepositoryImpl.deploy(boolean):513), because the location of the bundle
is provided by the bundlerepository.
Finally, I think that would be useful to have a way to track where the
bundle came from, but it also useful to have an URL which do not depend
from the bundle-version so that make easy the update of the bundle.
>
> Alin Dreghiciu
>
>
> On 9/12/07, Clement Escoffier <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>>
>>> -----Message d'origine-----
>>> De: Alin Dreghiciu [mailto:[EMAIL PROTECTED]
>>> Envoyé: mardi 11 septembre 2007 17:57
>>> À: dev@felix.apache.org
>>> Objet: Re: Maven-OBR-Plugin
>>>
>>> <http://wiki.ops4j.org/confluence/x/EoA6>You may also maybe take a look
>>> at
>>> http://wiki.ops4j.org/confluence/x/EoA6
>>> It has a different meaning but if could be related / reuse parts of it
>>> as I
>>> suppose you are targeting a strategy where the bundle deployed via OBR
>>> will
>>> have a specific url that helps in discovery or it may be that uses the
>>> proposed syntax from the wiki page and have just a specific repository
>>> and a
>>> requirement on a unique id from that that repository.
>>
>> That is a very interesting work. I develop the OBR url handler very
>> quickly
>> just to help bundle update (just to support command as 'update 8'). You
>> handler provide a useful functionality form more specific update. I will
>> reuse some part of you handler to support this kind of update.
>>
>>
>>> Can you implement it in such a way that is not dependent on felix or
>>> the
>>> bundle repository implementation form felix so it could be reused?
>> I am not sure it is really possible to be independent form the felix OBR
>> implementation. Indeed, the input URL that I receive it composed as
>> following :
>> obr://<bundle-symbolic-name>/<time-in-millis> (where time-in-millis
is the
>> time when the bundle was deployed).
>>
>> This syntax is specific to each implementation (I guess). So, the
handler
>> parse it to gather the symbolic name and look inside OBR repositories to
>> look for a resource with the same symbolic-name.
>>
>>
>> Clement
>>
>>> Alin Dreghiciu
>>>
>>> On 9/11/07, Clement Escoffier <[EMAIL PROTECTED]> wrote:
>>>> Hello,
>>>>
>>>>
>>>>
>>>> Just to announce that I commit two projects in my sandbox :
>>>>
>>>> - The maven-obr-plugin : creating OBR repository
>>> automatically
>>>> when
>>>> you install or deploy 'bundle' artifacts.
>>>>
>>>> - A obr:// URL Handler : useful to avoid the malformed URL
>>> error
>>>> when updating a bundle deployed with OBR (it discovers the update-
>>> location
>>>> inside OBR repositories).
>>>>
>>>>
>>>>
>>>> The second project becomes useful if you use the first one and you
>>> deploy
>>>> often your bundles with OBR.
>>>>
>>>>
>>>>
>>>> Clement
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Clement Escoffier
>>>>
>>>> Grenoble University
>>>>
>>>> +33 (0) 4 76 51 40 24
>>>>
>>>> http://clement.plop-plop.net
>>>>
>>>>
>>>>
>>>>
>>
>
