Re: Features and OBR (was Re: A Basic OBR Question)

[Jean-Baptiste Onofré]

Hi Gareth,

good catch. Could you create a Jira about that ?

Thanks,
Regards
JB

On 08/22/2012 10:36 PM, Gareth wrote:

OK, now I think I understand. Looking at ObrResolver.java and
BundleInfo.java:

  public List<BundleInfo> resolve(Feature feature) throws Exception {
     .
     .
     for (BundleInfo bundleInfo : feature.getBundles()) {
     .
     .
     }
     .
     .
     for (Resource res : deploy) {  << list of resolved resources from OBR
     .
     .
         if (info == null) {
             info = new BundleInfoImpl(res.getURI());
         }
         bundles.add(info);
     }
     return bundles;
}

If I now go to BundleInfoImpl.java start is implicitly set to false by
default (it should really be set explicitly) which explains why the
dependent bundles are not starting:

public class BundleInfoImpl implements BundleInfo {

     private int startLevel;
     private String location;
     private boolean start;
     private boolean dependency;
     .
     .
     .
     public BundleInfoImpl(String location) {
         this.location = location;
     }

Would it be possible to add a default "start" and "start-level" options to
the obr resolver so I can get these dependent bundles started? Or could this
somehow be set in the feature file as configuration values for each feature
(e.g. <feature...resolver=&quot;(obr)&quot; resolved-start=&quot;true&quot;
resolved-start-level=&quot;60&quot;>)? This would make the obr resolver far
more useful.

thanks in advance,
Gareth








--
View this message in context: 
http://karaf.922171.n3.nabble.com/A-Basic-OBR-Question-tp4025744p4025782.html
Sent from the Karaf - User mailing list archive at Nabble.com.

--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com