java - Pax-exam 4 no felix() method -

-

i had been using following code snippet osgi tests in eclipselink project pax exam 3.3.0:

@configuration public static option[] config() {     return options(             repositories("http://repo1.maven.org/maven2"),             mavenbundle().groupid("org.osgi").artifactid("org.osgi.compendium").version("4.3.0"),             mavenbundle().groupid("org.eclipse.persistence").artifactid("org.eclipse.persistence.asm")                     .version("2.5.1"),             //jaxb api             bundle("file:" + plugins_dir + "javax.xml.bind_2.2.12.v201410011542.jar"),             //ws api             bundle("file:" + plugins_dir + "javax.ws.rs_1.1.1.v20101004-1200.jar"),             //eclipselink bundles             bundle("file:" + plugins_dir + "org.eclipse.persistence.moxy_2.7.0." + qualifier + ".jar"),             bundle("file:" + plugins_dir + "org.eclipse.persistence.core_2.7.0." + qualifier + ".jar"),             bundle("file:" + plugins_dir + "org.eclipse.persistence.asm_5.0.1.v201405080102.jar"),              junitbundles(),             felix()); }

now, switched build jdk 8 , using pax exam 4.4.0, because pax exam 3.x not build jdk 8. issue pax exam 4 no longer provides convenient org.ops4j.pax.exam.coreoptions.felix() method. how can go around issue? goal run osgi tests least configuration possible.

if remove felix() method, following error:

running org.eclipse.persistence.testing.osgi.osgibundletest [main] info org.ops4j.pax.exam.spi.defaultexamsystem - pax exam system (version: 4.4.0) created. [main] info org.ops4j.pax.exam.junit.impl.proberunner - creating paxexam runner class org.eclipse.persistence.testing.osgi.osgibundletest tests run: 1, failures: 0, errors: 1, skipped: 0, time elapsed: 0.167 sec <<< failure! initializationerror(org.eclipse.persistence.testing.osgi.osgibundletest)  time elapsed: 0.01 sec  <<< error! org.ops4j.pax.exam.testcontainerexception: no service org.osgi.framework.launch.frameworkfactory found in meta-inf/services on classpath

thanks

felix() , other framework options have been deprecated long time ago, before pax exam 3.3.0, if remember correctly, i'm bit surprised version information.

anyway, if want run tests on felix, make sure felix osgi implementation on classpath, , that's it. no need explicit option.


Comments

Post a Comment

Popular posts from this blog

java - Custom OutputStreamAppender not run: LOGBACK: No context given for <MYAPPENDER> -

-
i wish write custom appender on basis of outputstreamappender . wrote following class package tests; import java.io.ioexception; import java.io.outputstream; import ch.qos.logback.core.outputstreamappender; public class myappender<e> extends outputstreamappender<e> { public myappender() { system.out.println("myappender created"); setoutputstream(new outputstream() { @override public void write(int b) throws ioexception { throw new unsupportedoperationexception(); } }); } } then wrote following runner: package tests; import org.slf4j.loggerfactory; import ch.qos.logback.classic.logger; public class runner { private static final logger log = (logger) loggerfactory.getlogger(runner.class); public static void main(string[] args) { //log.addappender(new myappender<iloggingevent>()); log.info("hello world"); } } finall...
Read more

java - UML - How would you draw a try catch in a sequence diagram? -

-
Image
is there standard way of drawing try catch sequence diagrams? i've made attempt based on this feel end result doesn't feel right. code diagram based around: public static void save () { try { filehandle filehandle = gdx.files.external(file); filehandle.writestring(boolean.tostring(constantshandler.soundenabled)+"\n", false); (int = 0; < 5; i++) { filehandle.writestring(integer.tostring(constantshandler.highscores[i])+"\n", true); } } catch (throwable e) { } } my attempt note: know still need add loop. that's ok. fragments meant show conditional control flow in sequence diagram. superstructures puts limitations on use of fragments (see pp. 467 of ss2.1.1). should use critical region try part above. , option catch . however, keep telling can take quite freedom in using uml. it's language , such changes in life time. long reader ge...
Read more

c++ - No viable overloaded operator for references a map -

-
i trying use map can make tag names reference number. when try , use it, in code error (6 in total every time reference map): src/main.cpp:25:45: error: no viable overloaded operator[] type 'std::map<std::string, std::string>' const char* idcs = node.child_value(tagmap[3]); this code: #include "pugi/pugixml.hpp" #include <iostream> #include <string> #include <map> int main() { pugi::xml_document doca, docb; std::map<std::string, pugi::xml_node> mapa, mapb; std::map<std::string, std::string> tagmap {{"1", "data"}, {"2", "entry"}, {"3", "id"}, {"4", "content"}}; if (!doca.load_file("a.xml") || !docb.load_file("b.xml")) { std::cout << "can't find input files"; return 1; } (auto& node: doca.child(tagmap[1]).children(tagmap[2])) { co...
Read more