When using the replaceConfigurationFile route my test never can connect
to RMI.
It seems to fail after this
2015-08-31 16:01:10,692 | INFO | pool-31-thread-1 | TldScanner | 106 -
org.ops4j.pax.web.pax-web-jsp - 4.2.0 | found TLD
bundle://106.0:0/META-INF/x.tld
2015-08-31 16:01:10,707 | INFO | pool-31-thread-1 | ContextHandler | 87
- org.eclipse.jetty.util - 9.2.10.v20150310 | Started
HttpServiceContext{httpContext=DefaultHttpContext
[bundle=org.apache.karaf.webconsole.gogo [65], contextID=default]}
When I have the same features as in the cfg file added through the
KarafDistributionOption.features method everything seems to work ok. Is
there not a way to specify boot order while using the
KarafDistributionOption.features code.
On 2015-08-31 14:54, [email protected] wrote:
> Ok. I will use that method and the replaceconfigurationfile option in
> paxexam. Thank you for that help. I am going under the assumption that things
> specified like KarafDistributionOption.features(karafStandardRepo, "wrap") in
> the options section of paxexam will run after all the things specified in the
> featuresBoot section of the org.apache.karaf.features.cfg file.
>
> Thank you for all your help.
>
> On 2015-08-31 14:49, Jean-Baptiste Onofré wrote:
>
> In the featuresBoot, you can define stage:
>
> featuresBoot=(aries-blueprint),camel-blueprint
>
> like this, aries-bluerint is installed in the stage earlier than
> camel-blueprint.
>
> Regards
> JB
>
> On 08/31/2015 08:48 PM, [email protected] wrote:
> I have it in there in my custom build but I have camel in there as well.
> Should camel be moved out and if so where can I put camel to be installed
> after the boot features. In my integration test how would I overwrite that
> file or specify which features are boot features. Thanks for any help, David
> On 2015-08-31 14:43, Jean-Baptiste Onofré wrote: You can define
> aries-blueprint as a boot features by update
> etc/org.apache.karaf.features.cfg. Regards JB On 08/31/2015 08:35
> PM,[email protected] <mailto:[email protected]> wrote:
> Aries-blueprint doesn't seem to be a prerequisite in camels features.xml but
> it is required for the camel feature in karaf 4.0.1.
> http://repo1.maven.org/maven2/org/apache/camel/karaf/apache-camel/2.15.3/apache-camel-2.15.3-features.xml
> [1] Is there a way in my test to make sure that aries-blueprint is loaded
> before camel. MavenArtifactUrlReference karafUrl =
CoreOptions.maven().groupId("org.apache.karaf").artifactId("apache-karaf").version("4.0.1").type("tar.gz");
MavenUrlReference karafStandardRepo = CoreOptions.maven()
.groupId("org.apache.karaf.features") .artifactId("standard") .version("4.0.1")
.classifier("features") .type("xml"); MavenUrlReference karafCxfRepo =
CoreOptions.maven() .groupId("org.apache.cxf.karaf") .artifactId("apache-cxf")
.version("3.1.2") .classifier("features") .type("xml"); MavenUrlReference
karafCamelRepo = CoreOptions.maven() .groupId("org.apache.camel.karaf")
.artifactId("apache-camel") .version("2.15.3") .classifier("features")
.type("xml"); return new Option[]{
KarafDistributionOption.karafDistributionConfiguration().frameworkUrl(karafUrl).name("Apache
Karaf"). unpackDirectory(new
File("target/paxexam/unpack")).useDeployFolder(false),
KarafDistributionOption.keepRuntimeFolder(),
CoreOptions.systemProperty("org.ops4j.pax.logging.DefaultServiceLog.level").value("DEBUG"),
CoreOptions.repository("http://artifactory.orbistechnologies.com/artifactory/repo
[2]").id("orbis").allowSnapshots(),
KarafDistributionOption.editConfigurationFilePut(CustomProperties.KARAF_FRAMEWORK,
"felix"), // disable JMX RBAC security, thanks to the KarafMBeanServerBuilder
KarafDistributionOption.configureSecurity().disableKarafMBeanServerBuilder(),
KarafDistributionOption.logLevel(LogLevel.INFO),
KarafDistributionOption.features(karafStandardRepo, "wrap"),
KarafDistributionOption.features(karafStandardRepo, "aries-blueprint"),
KarafDistributionOption.features(karafStandardRepo, "shell"),
KarafDistributionOption.features(karafStandardRepo, "shell-compat"),
KarafDistributionOption.features(karafStandardRepo, "feature"),
KarafDistributionOption.features(karafStandardRepo, "jaas"),
KarafDistributionOption.features(karafStandardRepo, "ssh"),
KarafDistributionOption.features(karafStandardRepo, "management"),
KarafDistributionOption.features(karafStandardRepo, "bundle"),
KarafDistributionOption.features(karafStandardRepo, "config"),
KarafDistributionOption.features(karafStandardRepo, "deployer"),
KarafDistributionOption.features(karafStandardRepo, "diagnostic"),
KarafDistributionOption.features(karafStandardRepo, "feature"),
KarafDistributionOption.features(karafStandardRepo, "instance"),
KarafDistributionOption.features(karafStandardRepo, "kar"),
KarafDistributionOption.features(karafStandardRepo, "log"),
KarafDistributionOption.features(karafStandardRepo, "package"),
KarafDistributionOption.features(karafStandardRepo, "service"),
KarafDistributionOption.features(karafStandardRepo, "system"),
KarafDistributionOption.features(karafStandardRepo, "war"),
KarafDistributionOption.features(karafStandardRepo, "webconsole"),
KarafDistributionOption.features(karafStandardRepo, "scr"),
KarafDistributionOption.features(karafStandardRepo, "transaction"),
KarafDistributionOption.features(karafCxfRepo, "cxf-jaxrs"),
KarafDistributionOption.features(karafCamelRepo, "camel"),
KarafDistributionOption.features(karafFitRepo, "hazelcast"),
KarafDistributionOption.features(karafFitRepo, "rest-socket"),
KarafDistributionOption.features(karafFitRepo, "hadoop") }; }
Links:
------
[1]
http://repo1.maven.org/maven2/org/apache/camel/karaf/apache-camel/2.15.3/apache-camel-2.15.3-features.xml
[2] http://artifactory.orbistechnologies.com/artifactory/repo
