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

Kristian Koehler commented on FELIX-1000:
-----------------------------------------

Hi

two things I'm trying to achive here:
* eliminate the exception
* update the bundle
;-)

In my first scenario I deployed all my bundles through the OBR. I install them 
using maven in my local repo and the deploy them to Felix using OBR. Normal 
versions and SNAPSHOT versions. So an update of the same version means 
different things ;-). SNAPSHOTs are updated, normal versions "stay" the same.

Updating to a new (bundle) version may also be problematic, i think. Which 
version should be updated to? The newest or the next available. A customer has 
the requirement to update to the next available version and not to the newest. 
For example: currently version 1.1 is installed. Version 1.2, 1.3 and 2.0 are 
available from OBR. The customer wants to update to 1.2. 

Not sure if the update should try to use a newer version. If I'm right the none 
OBR stuff also doesn't try to update to a newer version...

Kristian

> 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, 
> FELIX-1000-23_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.

Reply via email to