Re: [equinox-dev] help understanding osgi.parentClassLoader

2008-06-02 Thread nebulae
I'm sorry I sent my email a little too fast, I still had the parentclassloader set as app. So now my question is how else can it work if I don't supply app has the loader given the scenario I described in my previous email. Thanks Shravan On Mon, Jun 2, 2008 at 2:38 PM, nebulae <[EMAIL PROTECT

Re: [equinox-dev] help understanding osgi.parentClassLoader

2008-06-02 Thread nebulae
Thanks a lot Tom, you're right xerces.jar was indeed in the ext dir and that's why osgi.parentClassloader=app worked and so would ext. I was able to fix this problem by supplying DynamicImport-Package: * in one of my bundles. Here are the details: I have a declarative service let's say in a bund

Re: [equinox-dev] help understanding osgi.parentClassLoader

2008-06-02 Thread Thomas Watson
[EMAIL PROTECTED] wrote on 06/01/2008 10:36:04 PM: > > Hi, > > I'm new to OSGI so please bear with me if they are basically naive questions. > I'm using Equinox's latest version, I've gone through the mailing > lists and OSGI's core manual especailly the Module layer section and > found lots of ver

[equinox-dev] help understanding osgi.parentClassLoader

2008-06-01 Thread nebulae
Hi, I'm new to OSGI so please bear with me if they are basically naive questions. I'm using Equinox's latest version, I've gone through the mailing lists and OSGI's core manual especailly the Module layer section and found lots of very important information. Under Eclipse's runtime options there