> I'm doing it in my free time.
Wow! Must be nice to have free time. ;-) > how does the wrap handler work? > It implements the OSGi url handler and when requested it will take > the wrapped jar, use bnd to actually do the wrapping and give back an > input stream to the resulted OSGi bundle. What the "user" of the wrap: > url does with the input stream is not in the scope of wrap handler. In > runner, the input stream is saved to the cache folder as a file (jar) > and is passed to the target platform. Sorry, I don't understand. You say "take the wrapped jar", then you say "do the wrapping"... So, is the jar first wrapped, and you're just accessing the jar? Or, when the jar is requested, at runtime you use bnd to wrap the jar? I assume by "wrap" you mean include a manifest (and maybe an Activator??)... > Also, I'm going to be interested in the OBR hander... any > plans to > implement that in the next couple of months? > > > Yes. Cool! Please keep me informed. :-) Thanks, Alin. Dave _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
