On Sun, Aug 3, 2008 at 4:15 PM, <[EMAIL PROTECTED]> wrote:
> Ah..that makes sense! I don't know knopflerfish and other osgi
> implementations, but I can imagine that they're some very delicate issues to
> resolve if you wnat a framework independent application, especially when
> using classloaders
riginal Message-
> From: [EMAIL PROTECTED] on behalf of Stuart McCulloch
> Sent: Sun 03/08/2008 16:50
> To: General OPS4J
> Subject: Re: Plugin Structure
>
> 2008/8/3 <[EMAIL PROTECTED]>
>
> > Hi,
> >
> > I have been working on understanding pax-we
om: [EMAIL PROTECTED] on behalf of Stuart McCulloch
Sent: Sun 03/08/2008 16:50
To: General OPS4J
Subject: Re: Plugin Structure
2008/8/3 <[EMAIL PROTECTED]>
> Hi,
>
> I have been working on understanding pax-web and pax-web-extender better,
> and I saw that sometimes jars in bund
2008/8/3 <[EMAIL PROTECTED]>
> Hi,
>
> I have been working on understanding pax-web and pax-web-extender better,
> and I saw that sometimes jars in bundles are packed double.
> For instance org.apache.commons is packed in the 0.5.0 version of
> pax-web-bundle-0.5.0.jar, while it is also imported
Hi,
I have been working on understanding pax-web and pax-web-extender better, and I
saw that sometimes jars in bundles are packed double.
For instance org.apache.commons is packed in the 0.5.0 version of
pax-web-bundle-0.5.0.jar, while it is also imported as a required plugin in the
manifest. T
