felix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Pauls <karlpa...@gmail.com>
Subject Re: OSGi bundles and Pack200 format with Bundle-Classpath
Date Fri, 04 May 2012 10:34:43 GMT
your handler would need to read the bundle-classpath and on the fly
and transparently need to unpack the pack200 entries inplace while the
bundle gets installed.



On Fri, May 4, 2012 at 10:18 AM, Christopher BROWN <brown@reflexe.fr> wrote:
> I understand the protocol handler for loading bundles, but here I'm
> referring to embedded JARs within a bundle loaded using the
> Bundle-Classpath manifest header.  So I foresee two issues:
> • Bundle-Classpath might refuse to load "myJar.jar.pack.gz" because of the
> Pack200 extension (it's not plain ".jar")
> • even if it did this in a portable way, I don't see how to specify that it
> should use my protocol handler (e.g. "pack200:") instead of the default
> protocol handler used by the framework when loading the bundle that
> contains the Bundle-Classpath header.
> Thanks,
> Christopher
> On 4 May 2012 10:10, Karl Pauls <karlpauls@gmail.com> wrote:
>> On Fri, May 4, 2012 at 9:46 AM, Christopher BROWN <brown@reflexe.fr>
>> wrote:
>> > Would that be portable?
>> urlhandler services are part of the spec.
>> > Also, how would it distinguish the Bundle-Classpath of "my" bundles (the
>> > ones I could build containing embedded Pack200 JARs) from other bundles
>> > using Bundle-Classpath (i don't want to break default behavior)?
>> you register a handler as a service together with its url prefix and
>> subsequently, you install your bundles with that prefix e.g.;
>> install("pack200:mybundles/bundle-with-pack200.jar");
>> then, inside the handler, you would need to create a wrapper
>> connection that does do the unpack on the fly.

Karl Pauls

To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org

View raw message