I'm using Pax Runner (with Equinox) with a text list of bundles to load 
on startup. I've noticed that the bundle locations will differ depending 
on whether they were loaded at startup or manually loaded later.

For example, I have a bundle that I load from Maven with the following 
URL: mvn:com.habuma/configuration/2.0.0-beta61-2-SNAPSHOT

When I look at the bundle's location (using the "bundle" command in 
Equinox), it tells me the following: 
[EMAIL PROTECTED]:file:com.habuma.Configuration_2.0.0.jar/ [14]

Alright...then later I uninstall and reinstall the same bundle (using 
the uninstall/install commands in Equinox and leaning on Pax URL to 
resolve from Maven)...here's what I see for the location: 
mvn:com.habuma/configuration/2.0.0-beta61-2-SNAPSHOT [64]

I have a variety of troubles with the initial location, but really like 
what I see after I do a reinstall. The most significant difference is 
that with the former I can't do a hot-update, but have no problems with 
hot-updates on the latter. I'm also facing problems with the former 
version containing colons, as I have a WAR bundle that I'm deploying to 
Tomcat (ala, the latest Spring-DM 1.1.0-m2 way of deploying web bundles) 
and the colons interfere with Tomcat's desire to register the WAR file 
as an MBean in JMX (but this is the lesser of the problems).

Is there any way to get Pax Runner to install bundles the same way that 
Equinox does with Pax URL? That is, to *not* set the bundle location to  
"[EMAIL PROTECTED]" and to keep the original location?



_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to