You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Dean Schulze <de...@gmail.com> on 2014/12/12 06:41:16 UTC
Loading a class from a different bundle dynamically
I have an OSGI app consisting of several bundles. In order to do
functional testing I want to dynamically load test case classes when the
-Dtest.class.name=MyTestClass property is set. I want to keep the test
classes in their own bundle to make it easy to exclude them from the
production binary. The only test artifact that will be in the
production code bundles will be an interface that the test classes
implement.
The test bundle depends on the production bundles to access the test
interface and because the test classes also use other classes in the
production bundles. The test classes themselves are POJOs. They are
not Serice or Component classes. I only want to load them when the
test.class.name property is set so I don't want Felix injecting them.
I try to load the test class
public class MyTestClass implements MyTestClassI {
....
}
from the production bundle code like this
MyTestClassI myTestClass;
....
// Inside the @Activate method
String testClassName = System.getProperty("test.class.name");
if (testClassName != null) {
Class c = Class.forName(testClassName);
myTestClass = c.newInstance();
}
This gives a ClassNotFoundException.
The recommended solution that I've seen to this problem is to use the
Bundle.loadClass() method, but I haven't seen any example code that
actually does this. I would have to get the test Bundle first and I
haven't been able to find out how to do this.
If anyone knows of example code to do dynamic class loading in Felix I
would appreciate a link to it. If this kind of dynamic loading can only
be done form the gogo shell I could live with that since this would only
be done by the development and test teams.
Thanks.
Dean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Loading a class from a different bundle dynamically
Posted by David Jencks <da...@yahoo.com.INVALID>.
I don't understand what you are trying to do yet, but you might investigate putting your test classes in a fragment bundle (only loaded when testing, but then "part" of your main bundle) and also mocking the external input so it is under better control (although calling the result a functional test would be a stretch).
david jencks
On Dec 12, 2014, at 9:31 AM, Achim Nierbeck <bc...@googlemail.com> wrote:
> Dynamic Import?
> Add a manifest header or dynamically importing your testclass in case it's
> available,
> but I would actually work with a service tracker that waits for the
> "testservice" to be available and trigger the "test" then.
>
> regards, Achim
>
>
> 2014-12-12 15:24 GMT+01:00 Dean Schulze <de...@gmail.com>:
>
>> I don't think Pax Exam addresses my issue.
>>
>> A little more explanation may help.
>>
>> This system is driven by both external input and user input. The
>> external input will be the same on each test run. Controlling the
>> timing of the user input -- synchronizing it with the external input --
>> is the problem. The typical unit test case is only driven by user input
>> so timing doesn't matter.
>>
>> Think of triggering a calculation where your inputs change constantly.
>> The calculation is different each time and in order to verify it I have
>> to trigger the calculation at exactly the same times on each test run.
>>
>> My test classes have to monitor the internal state of my application to
>> synchronize with the external input in order to make them repeatable.
>> Without that synchronization automated testing will be impossible.
>>
>> I don't want to put the test classes into the production bundles which
>> is why I'm trying to load them dynamically when the system is under
>> test.
>>
>>
>> On Fri, 2014-12-12 at 08:38 +0100, Achim Nierbeck wrote:
>>> Hi,
>>>
>>> just one quick question/hint.
>>> You are aware of the Pax Exam Testframework?
>>> I think with it you are able to do what you are looking for.
>>>
>>> regards, Achim
>>>
>>>
>>> 2014-12-12 6:41 GMT+01:00 Dean Schulze <de...@gmail.com>:
>>>
>>>>
>>>> I have an OSGI app consisting of several bundles. In order to do
>>>> functional testing I want to dynamically load test case classes when
>> the
>>>> -Dtest.class.name=MyTestClass property is set. I want to keep the
>> test
>>>> classes in their own bundle to make it easy to exclude them from the
>>>> production binary. The only test artifact that will be in the
>>>> production code bundles will be an interface that the test classes
>>>> implement.
>>>>
>>>> The test bundle depends on the production bundles to access the test
>>>> interface and because the test classes also use other classes in the
>>>> production bundles. The test classes themselves are POJOs. They are
>>>> not Serice or Component classes. I only want to load them when the
>>>> test.class.name property is set so I don't want Felix injecting them.
>>>>
>>>> I try to load the test class
>>>>
>>>> public class MyTestClass implements MyTestClassI {
>>>> ....
>>>> }
>>>>
>>>> from the production bundle code like this
>>>>
>>>> MyTestClassI myTestClass;
>>>>
>>>> ....
>>>>
>>>> // Inside the @Activate method
>>>> String testClassName = System.getProperty("test.class.name");
>>>> if (testClassName != null) {
>>>>
>>>> Class c = Class.forName(testClassName);
>>>> myTestClass = c.newInstance();
>>>> }
>>>>
>>>> This gives a ClassNotFoundException.
>>>>
>>>> The recommended solution that I've seen to this problem is to use the
>>>> Bundle.loadClass() method, but I haven't seen any example code that
>>>> actually does this. I would have to get the test Bundle first and I
>>>> haven't been able to find out how to do this.
>>>>
>>>> If anyone knows of example code to do dynamic class loading in Felix I
>>>> would appreciate a link to it. If this kind of dynamic loading can
>> only
>>>> be done form the gogo shell I could live with that since this would
>> only
>>>> be done by the development and test teams.
>>>>
>>>> Thanks.
>>>>
>>>> Dean
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>>> For additional commands, e-mail: users-help@felix.apache.org
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
>
>
> --
>
> Apache Member
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
>
> Software Architect / Project Manager / Scrum Master
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Loading a class from a different bundle dynamically
Posted by Chetan Mehrotra <ch...@gmail.com>.
Also have a look at Sling Testing Tools [1]
Chetan Mehrotra
[1] http://sling.apache.org/documentation/development/sling-testing-tools.html
On Sat, Dec 13, 2014 at 2:05 AM, Christian Schneider
<ch...@die-schneider.net> wrote:
> You can also do this without an Activator and just DS.
>
> On the production side you have to find a way to listen for 0..n services
> that implement an interface.
> http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html
> http://www.aqute.biz/Bnd/Components
> You will need @Reference and the bind and unbind attributes. So you can
> react when test Services are published or removed.
>
> On the test side you simply publish the test class as a service
> @Component
> @Service(interfaces = TestInterface.class)
> public class Testclass implements TestInterface {
> ...
> }
>
> What you do is an implementation of the whiteboard pattern.
>
> Christian
>
> Am 12.12.2014 19:06, schrieb Dean Schulze:
>
>> I don't know what you mean when you say instantiate the class in the
>> Activator. The Activator runs after the @Reference classes have been
>> injected. I tried to load the test classes dynamically in the Activator,
>> but I got a ClassNotFoundException.
>>
>> In order to get the implementation below to work the production module
>> depends on the test module, but the test module depends on the production
>> module, which won't work.
>>
>> This approach probably can't be made to work.
>>
>> As an alternative I can move the test classes into their own package in
>> the
>> production module and have maven exclude that package from the production
>> binary.
>>
>> @Component
>> @Service { .....}
>> public class ProductionClass implements ... {
>>
>> private @Reference ITestClass testClass;
>>
>> @Activate
>> public void activate() {
>>
>> }
>>
>>
>> }
>>
>>
>> On Fri, Dec 12, 2014 at 7:41 AM, Christian Schneider <
>> chris@die-schneider.net> wrote:
>>>
>>> I also recommend to use a service for this.
>>>
>>> Simply put your test class into a separate bundle. In the activator
>>> instantiate the test class and publish it as a service using the test
>>> interface you provide.
>>>
>>> The production bundle would then listen for services implementing the
>>> test
>>> interface e.g. using a service tracker and call them.
>>>
>>> This has the advantage that you do not need any system property and class
>>> loading specialities. Another advantage is that you can start the test by
>>> deploying the test bundle and stop it again by removing it.
>>> So no restart required.
>>>
>>> Christian
>>>
>>>
>>> On 12.12.2014 15:31, Achim Nierbeck wrote:
>>>
>>>> Dynamic Import?
>>>> Add a manifest header or dynamically importing your testclass in case
>>>> it's
>>>> available,
>>>> but I would actually work with a service tracker that waits for the
>>>> "testservice" to be available and trigger the "test" then.
>>>>
>>>> regards, Achim
>>>>
>>>>
>>>>
>>> --
>>> Christian Schneider
>>> http://www.liquid-reality.de
>>>
>>> Open Source Architect
>>> http://www.talend.com
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>>> For additional commands, e-mail: users-help@felix.apache.org
>>>
>>>
>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Loading a class from a different bundle dynamically
Posted by Christian Schneider <ch...@die-schneider.net>.
You can also do this without an Activator and just DS.
On the production side you have to find a way to listen for 0..n
services that implement an interface.
http://felix.apache.org/documentation/subprojects/apache-felix-maven-scr-plugin/scr-annotations.html
http://www.aqute.biz/Bnd/Components
You will need @Reference and the bind and unbind attributes. So you can
react when test Services are published or removed.
On the test side you simply publish the test class as a service
@Component
@Service(interfaces = TestInterface.class)
public class Testclass implements TestInterface {
...
}
What you do is an implementation of the whiteboard pattern.
Christian
Am 12.12.2014 19:06, schrieb Dean Schulze:
> I don't know what you mean when you say instantiate the class in the
> Activator. The Activator runs after the @Reference classes have been
> injected. I tried to load the test classes dynamically in the Activator,
> but I got a ClassNotFoundException.
>
> In order to get the implementation below to work the production module
> depends on the test module, but the test module depends on the production
> module, which won't work.
>
> This approach probably can't be made to work.
>
> As an alternative I can move the test classes into their own package in the
> production module and have maven exclude that package from the production
> binary.
>
> @Component
> @Service { .....}
> public class ProductionClass implements ... {
>
> private @Reference ITestClass testClass;
>
> @Activate
> public void activate() {
>
> }
>
>
> }
>
>
> On Fri, Dec 12, 2014 at 7:41 AM, Christian Schneider <
> chris@die-schneider.net> wrote:
>> I also recommend to use a service for this.
>>
>> Simply put your test class into a separate bundle. In the activator
>> instantiate the test class and publish it as a service using the test
>> interface you provide.
>>
>> The production bundle would then listen for services implementing the test
>> interface e.g. using a service tracker and call them.
>>
>> This has the advantage that you do not need any system property and class
>> loading specialities. Another advantage is that you can start the test by
>> deploying the test bundle and stop it again by removing it.
>> So no restart required.
>>
>> Christian
>>
>>
>> On 12.12.2014 15:31, Achim Nierbeck wrote:
>>
>>> Dynamic Import?
>>> Add a manifest header or dynamically importing your testclass in case it's
>>> available,
>>> but I would actually work with a service tracker that waits for the
>>> "testservice" to be available and trigger the "test" then.
>>>
>>> regards, Achim
>>>
>>>
>>>
>> --
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Open Source Architect
>> http://www.talend.com
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Loading a class from a different bundle dynamically
Posted by Dean Schulze <de...@gmail.com>.
I don't know what you mean when you say instantiate the class in the
Activator. The Activator runs after the @Reference classes have been
injected. I tried to load the test classes dynamically in the Activator,
but I got a ClassNotFoundException.
In order to get the implementation below to work the production module
depends on the test module, but the test module depends on the production
module, which won't work.
This approach probably can't be made to work.
As an alternative I can move the test classes into their own package in the
production module and have maven exclude that package from the production
binary.
@Component
@Service { .....}
public class ProductionClass implements ... {
private @Reference ITestClass testClass;
@Activate
public void activate() {
}
}
On Fri, Dec 12, 2014 at 7:41 AM, Christian Schneider <
chris@die-schneider.net> wrote:
>
> I also recommend to use a service for this.
>
> Simply put your test class into a separate bundle. In the activator
> instantiate the test class and publish it as a service using the test
> interface you provide.
>
> The production bundle would then listen for services implementing the test
> interface e.g. using a service tracker and call them.
>
> This has the advantage that you do not need any system property and class
> loading specialities. Another advantage is that you can start the test by
> deploying the test bundle and stop it again by removing it.
> So no restart required.
>
> Christian
>
>
> On 12.12.2014 15:31, Achim Nierbeck wrote:
>
>> Dynamic Import?
>> Add a manifest header or dynamically importing your testclass in case it's
>> available,
>> but I would actually work with a service tracker that waits for the
>> "testservice" to be available and trigger the "test" then.
>>
>> regards, Achim
>>
>>
>>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
Re: Loading a class from a different bundle dynamically
Posted by Christian Schneider <ch...@die-schneider.net>.
I also recommend to use a service for this.
Simply put your test class into a separate bundle. In the activator
instantiate the test class and publish it as a service using the test
interface you provide.
The production bundle would then listen for services implementing the
test interface e.g. using a service tracker and call them.
This has the advantage that you do not need any system property and
class loading specialities. Another advantage is that you can start the
test by deploying the test bundle and stop it again by removing it.
So no restart required.
Christian
On 12.12.2014 15:31, Achim Nierbeck wrote:
> Dynamic Import?
> Add a manifest header or dynamically importing your testclass in case it's
> available,
> but I would actually work with a service tracker that waits for the
> "testservice" to be available and trigger the "test" then.
>
> regards, Achim
>
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Loading a class from a different bundle dynamically
Posted by Achim Nierbeck <bc...@googlemail.com>.
Dynamic Import?
Add a manifest header or dynamically importing your testclass in case it's
available,
but I would actually work with a service tracker that waits for the
"testservice" to be available and trigger the "test" then.
regards, Achim
2014-12-12 15:24 GMT+01:00 Dean Schulze <de...@gmail.com>:
> I don't think Pax Exam addresses my issue.
>
> A little more explanation may help.
>
> This system is driven by both external input and user input. The
> external input will be the same on each test run. Controlling the
> timing of the user input -- synchronizing it with the external input --
> is the problem. The typical unit test case is only driven by user input
> so timing doesn't matter.
>
> Think of triggering a calculation where your inputs change constantly.
> The calculation is different each time and in order to verify it I have
> to trigger the calculation at exactly the same times on each test run.
>
> My test classes have to monitor the internal state of my application to
> synchronize with the external input in order to make them repeatable.
> Without that synchronization automated testing will be impossible.
>
> I don't want to put the test classes into the production bundles which
> is why I'm trying to load them dynamically when the system is under
> test.
>
>
> On Fri, 2014-12-12 at 08:38 +0100, Achim Nierbeck wrote:
> > Hi,
> >
> > just one quick question/hint.
> > You are aware of the Pax Exam Testframework?
> > I think with it you are able to do what you are looking for.
> >
> > regards, Achim
> >
> >
> > 2014-12-12 6:41 GMT+01:00 Dean Schulze <de...@gmail.com>:
> >
> > >
> > > I have an OSGI app consisting of several bundles. In order to do
> > > functional testing I want to dynamically load test case classes when
> the
> > > -Dtest.class.name=MyTestClass property is set. I want to keep the
> test
> > > classes in their own bundle to make it easy to exclude them from the
> > > production binary. The only test artifact that will be in the
> > > production code bundles will be an interface that the test classes
> > > implement.
> > >
> > > The test bundle depends on the production bundles to access the test
> > > interface and because the test classes also use other classes in the
> > > production bundles. The test classes themselves are POJOs. They are
> > > not Serice or Component classes. I only want to load them when the
> > > test.class.name property is set so I don't want Felix injecting them.
> > >
> > > I try to load the test class
> > >
> > > public class MyTestClass implements MyTestClassI {
> > > ....
> > > }
> > >
> > > from the production bundle code like this
> > >
> > > MyTestClassI myTestClass;
> > >
> > > ....
> > >
> > > // Inside the @Activate method
> > > String testClassName = System.getProperty("test.class.name");
> > > if (testClassName != null) {
> > >
> > > Class c = Class.forName(testClassName);
> > > myTestClass = c.newInstance();
> > > }
> > >
> > > This gives a ClassNotFoundException.
> > >
> > > The recommended solution that I've seen to this problem is to use the
> > > Bundle.loadClass() method, but I haven't seen any example code that
> > > actually does this. I would have to get the test Bundle first and I
> > > haven't been able to find out how to do this.
> > >
> > > If anyone knows of example code to do dynamic class loading in Felix I
> > > would appreciate a link to it. If this kind of dynamic loading can
> only
> > > be done form the gogo shell I could live with that since this would
> only
> > > be done by the development and test teams.
> > >
> > > Thanks.
> > >
> > > Dean
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > > For additional commands, e-mail: users-help@felix.apache.org
> > >
> > >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master
Re: Loading a class from a different bundle dynamically
Posted by Dean Schulze <de...@gmail.com>.
I don't think Pax Exam addresses my issue.
A little more explanation may help.
This system is driven by both external input and user input. The
external input will be the same on each test run. Controlling the
timing of the user input -- synchronizing it with the external input --
is the problem. The typical unit test case is only driven by user input
so timing doesn't matter.
Think of triggering a calculation where your inputs change constantly.
The calculation is different each time and in order to verify it I have
to trigger the calculation at exactly the same times on each test run.
My test classes have to monitor the internal state of my application to
synchronize with the external input in order to make them repeatable.
Without that synchronization automated testing will be impossible.
I don't want to put the test classes into the production bundles which
is why I'm trying to load them dynamically when the system is under
test.
On Fri, 2014-12-12 at 08:38 +0100, Achim Nierbeck wrote:
> Hi,
>
> just one quick question/hint.
> You are aware of the Pax Exam Testframework?
> I think with it you are able to do what you are looking for.
>
> regards, Achim
>
>
> 2014-12-12 6:41 GMT+01:00 Dean Schulze <de...@gmail.com>:
>
> >
> > I have an OSGI app consisting of several bundles. In order to do
> > functional testing I want to dynamically load test case classes when the
> > -Dtest.class.name=MyTestClass property is set. I want to keep the test
> > classes in their own bundle to make it easy to exclude them from the
> > production binary. The only test artifact that will be in the
> > production code bundles will be an interface that the test classes
> > implement.
> >
> > The test bundle depends on the production bundles to access the test
> > interface and because the test classes also use other classes in the
> > production bundles. The test classes themselves are POJOs. They are
> > not Serice or Component classes. I only want to load them when the
> > test.class.name property is set so I don't want Felix injecting them.
> >
> > I try to load the test class
> >
> > public class MyTestClass implements MyTestClassI {
> > ....
> > }
> >
> > from the production bundle code like this
> >
> > MyTestClassI myTestClass;
> >
> > ....
> >
> > // Inside the @Activate method
> > String testClassName = System.getProperty("test.class.name");
> > if (testClassName != null) {
> >
> > Class c = Class.forName(testClassName);
> > myTestClass = c.newInstance();
> > }
> >
> > This gives a ClassNotFoundException.
> >
> > The recommended solution that I've seen to this problem is to use the
> > Bundle.loadClass() method, but I haven't seen any example code that
> > actually does this. I would have to get the test Bundle first and I
> > haven't been able to find out how to do this.
> >
> > If anyone knows of example code to do dynamic class loading in Felix I
> > would appreciate a link to it. If this kind of dynamic loading can only
> > be done form the gogo shell I could live with that since this would only
> > be done by the development and test teams.
> >
> > Thanks.
> >
> > Dean
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> > For additional commands, e-mail: users-help@felix.apache.org
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Loading a class from a different bundle dynamically
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
just one quick question/hint.
You are aware of the Pax Exam Testframework?
I think with it you are able to do what you are looking for.
regards, Achim
2014-12-12 6:41 GMT+01:00 Dean Schulze <de...@gmail.com>:
>
> I have an OSGI app consisting of several bundles. In order to do
> functional testing I want to dynamically load test case classes when the
> -Dtest.class.name=MyTestClass property is set. I want to keep the test
> classes in their own bundle to make it easy to exclude them from the
> production binary. The only test artifact that will be in the
> production code bundles will be an interface that the test classes
> implement.
>
> The test bundle depends on the production bundles to access the test
> interface and because the test classes also use other classes in the
> production bundles. The test classes themselves are POJOs. They are
> not Serice or Component classes. I only want to load them when the
> test.class.name property is set so I don't want Felix injecting them.
>
> I try to load the test class
>
> public class MyTestClass implements MyTestClassI {
> ....
> }
>
> from the production bundle code like this
>
> MyTestClassI myTestClass;
>
> ....
>
> // Inside the @Activate method
> String testClassName = System.getProperty("test.class.name");
> if (testClassName != null) {
>
> Class c = Class.forName(testClassName);
> myTestClass = c.newInstance();
> }
>
> This gives a ClassNotFoundException.
>
> The recommended solution that I've seen to this problem is to use the
> Bundle.loadClass() method, but I haven't seen any example code that
> actually does this. I would have to get the test Bundle first and I
> haven't been able to find out how to do this.
>
> If anyone knows of example code to do dynamic class loading in Felix I
> would appreciate a link to it. If this kind of dynamic loading can only
> be done form the gogo shell I could live with that since this would only
> be done by the development and test teams.
>
> Thanks.
>
> Dean
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
> For additional commands, e-mail: users-help@felix.apache.org
>
>
--
Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>
Software Architect / Project Manager / Scrum Master