Yes, Jars inside Bundles are not uncommon (=supported) in OSGi. Check
out the meaning of Bundle-Classpath Header.
It just has the quirk that you should not use those bundles now as
compile time dependencies anymore (Java Compiler != Bundle Rules).
("Leaf Artifact")
Toni
On Wed, Sep 29, 2010 at 11:52 AM, Stijn de Witt <[email protected]> wrote:
> I've missed out on this subtlety until now, but if I get what you are saying
> correctly Richard, then nested JAR's (JAR inside a JAR) are supported in OSGi
> right?
>
> If so that would be GREAT! I always hated that there was no support for this
> by default in Java.
>
> -Stijn
>
>
> -----Original Message-----
> From: Richard S. Hall [mailto:[email protected]]
> Sent: maandag 27 september 2010 15:56
> To: [email protected]
> Subject: Re: 3rd party jars...
>
> On 9/26/10 23:52, Tony Anecito wrote:
>> Hi All,
>>
>> If you have a 3rd party jar how does it get included? Seems like OSGi
>> requires
>> the manifest to be modified which might be an issue. When "bundled" is there
>> another manifest created for OSGi?
>
> You can wrap a JAR file in a bundle JAR file by embedding it unchanged
> and put the OSGi metadata in the outer JAR manifest (including adding
> the embedded JAR file on the bundle class path).
>
> -> richard
>
>> Thanks,
>> -Tony
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Toni Menzel || http://okidokiteam.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
