A bundle has a property location. This is where the framework tries to
load the update from.
In Karaf you see this using list -u
karaf@root> list -u
START LEVEL 100 , List Threshold: 50
ID State Blueprint Level Update location
[ 86] [Active ] [ ] [ 80] mvn:com.vaadin/vaadin/6.7.1
[ 95] [Active ] [ ] [ 80]
mvn:net.lr/vaadinbridge/0.0.1-SNAPSHOT
[ 97] [Active ] [Created ] [ 80]
mvn:net.lr/vaadinexample1/0.0.1-SNAPSHOT
So update 97 would look in the maven repo for the jar to update.
Christian
Am 11.05.2012 15:19, schrieb Thierry Templier:
Thanks Christian for your answer and I'm pleased to hear that you made
work my use case ;-)
I'll read your tutorial... What do you exactly mean by "update location"?
Thierry
Btw. your use case looks exactly like what pax web does :-)
I have a tutorial where this is shown:
http://www.liquid-reality.de/display/liquid/2011/02/15/Karaf+Tutorial+Part+1+-+Installation+and+First+application
It also shows how to use the whiteboard extender that publishes
Services of type javax.servlet to the HttpService.
What is the update location of your bundle? Update only works if the
update location is where your updated bundle is located.
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
