felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1000) Updating an bundle which was installed via OBR fails
Date Tue, 21 Apr 2009 13:00:49 GMT

    [ https://issues.apache.org/jira/browse/FELIX-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701149#action_12701149

Richard S. Hall commented on FELIX-1000:

I don't think such an approach makes sense.

The whole reason why the OBR location string is meaningless is because there cannot be a relationship
between what the location is and what is installed there. While perhaps the symbolic name
and time stamp portions of the URL make sense in your URL, the "real URL" does not. As soon
as you update, then it is no longer the real URL, nor would it be the version specified in
the real URL. Remember, the location will never change.

That is why we ended up with a location that means nothing. Probably a better approach is
to have the URL handler use the location to look up the bundle and just query the metadata
about the bundle, e.g., its symbolic name and version. Then use this metadata to determine
how to update the bundle from OBR.

> Updating an bundle which was installed via OBR fails
> ----------------------------------------------------
>                 Key: FELIX-1000
>                 URL: https://issues.apache.org/jira/browse/FELIX-1000
>             Project: Felix
>          Issue Type: Bug
>          Components: Bundle Repository (OBR)
>            Reporter: Kristian Koehler
>         Attachments: FELIX-1000-21_04_2009.patch.txt
> Updating an bundle which was installed via the obr functionality results in an exception
(update was triggered via the shell):
> --- 8< ---
> java.net.MalformedURLException: Unknown protocol: obr
> 	at java.net.URL.<init>(URL.java:601)
> 	at java.net.URL.<init>(URL.java:464)
> 	at java.net.URL.<init>(URL.java:413)
> 	at org.apache.felix.framework.cache.JarRevision.initialize(JarRevision.java:149)
> 	at org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:78)
> 	at org.apache.felix.framework.cache.JarRevision.<init>(JarRevision.java:56)
> 	at org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:986)
> 	at org.apache.felix.framework.cache.BundleArchive.revise(BundleArchive.java:614)
> 	at org.apache.felix.framework.BundleImpl.revise(BundleImpl.java:916)
> 	at org.apache.felix.framework.Felix.updateBundle(Felix.java:1592)
> 	at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:792)
> 	at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:779)
> 	at org.apache.felix.shell.impl.UpdateCommandImpl.execute(UpdateCommandImpl.java:96)
> 	at org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Activator.java:276)
> 	at org.apache.felix.shell.tui.Activator$ShellTuiRunnable.run(Activator.java:167)
> 	at java.lang.Thread.run(Thread.java:619)
> --- 8< ---

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message