As it turned out, the problem with "factory already defined" was a red herring. It had to do with the fact that I was b=not stopping my framework when my test completed. And in my setup (I am using scala sbt to run tests), the factory hung around from one test to another. Stopping the framework in the test solved that problem. Sorry for the false alarm.
Azad jbonofre wrote > Hi Azad, > > Did you take a look on karaf-pax-exam ? > > As I mentioned earlier, we tried pax exam and had issues that we could not > solve in reasonable time. The trial was done by a colleague of mine. So I > don't know the details. Is karaf-pax-exam different from just simple pax > exam? I am not really versed in pax. So please forgive the naive question. > > Thanks. > > Azad > > Regards > JB > > On 03/22/2013 05:12 PM, azadbolour wrote: >> >> Hi Achim, >> >> No worries. I am only looking into using Felix for testing: to embed an >> OSGI >> container in a test so the test does not have to rely on starting an >> external Karaf. We have tried pax exam for testing but had issues with >> dependencies. So I thought of trying a more direct approach of embedding >> Felix in a test. Unfortunately, I am also running into difficulties >> starting >> bundles in the embedded Felix. I get the error below which I have yet to >> figure out. Just FYI. Maybe someone has an idea how to fix this. >> >> Thanks again. >> >> Azad >> >> ERROR: Unable to start system bundle. (java.lang.Error: factory already >> defined) >> java.lang.Error: factory already defined >> at java.net.URL.setURLStreamHandlerFactory(URL.java:1077) >> at org.apache.felix.framework.URLHandlers. > <init> > (URLHandlers.java:178) -- View this message in context: http://karaf.922171.n3.nabble.com/embedding-karaf-tp4028257p4028311.html Sent from the Karaf - User mailing list archive at Nabble.com.
