You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Xiaohui Wu (JIRA)" <ji...@apache.org> on 2013/06/06 10:19:21 UTC

[jira] [Created] (CAMEL-6434) The configAdminFileName property does not be picked up when run command: mvn camel:run

Xiaohui Wu created CAMEL-6434:
---------------------------------

             Summary: The configAdminFileName property does not be picked up when run command: mvn camel:run
                 Key: CAMEL-6434
                 URL: https://issues.apache.org/jira/browse/CAMEL-6434
             Project: Camel
          Issue Type: Bug
          Components: tooling
         Environment: Fedora16,JDK1.6,
            Reporter: Xiaohui Wu
             Fix For: 2.12.0


When running command: mvn camel:run, I know that the config file name and PID can be passed through the configuration in pom.xml like :

			<plugin>
				<groupId>org.apache.camel</groupId>
				<artifactId>camel-maven-plugin</artifactId>
				<version>${camel.version}</version>
				<configuration>
					<useBlueprint>true</useBlueprint>
					<configAdminPid>ConfigApp</configAdminPid>
					<configAdminFileName>/opt/jboss-fuse/jboss-fuse-6.0.0.redhat-024/deploy/ConfigApp.cfg</configAdminFileName>
				</configuration>
			</plugin>
But when I tried to run the command: mvn camel:run to get the content from the config file, I found that only configAdminPid is recognized, while the configAdminFileName did not been picked up.

The stack trace is:
[ERROR] Error occurred while running main from: org.apache.camel.test.blueprint.Main
[ERROR] 
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.camel.maven.RunMojo$1.run(RunMojo.java:486)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IllegalArgumentException: The persistent file should not be null
	at org.apache.camel.test.blueprint.CamelBlueprintHelper.setPersistentFileForConfigAdmin(CamelBlueprintHelper.java:176)
	at org.apache.camel.test.blueprint.Main.doStart(Main.java:103)
	at org.apache.camel.support.ServiceSupport.start(ServiceSupport.java:61)
	at org.apache.camel.main.MainSupport.run(MainSupport.java:148)
	at org.apache.camel.main.MainSupport.run(MainSupport.java:343)
	at org.apache.camel.test.blueprint.Main.main(Main.java:81)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira