![]() | Subscription Only |
---|---|
This feature is only available to FuseSource subscribers. |
A Local Camel Context runtime profile configures how Apache Camel is
invoked to execute a route. A Local Camel Context runtime profile
stores the name of the context file in which your routes are defined, the name of the
main
to invoke, the command line options passed into the JVM, the
JRE to use, the classpath to use, any environment variables that need to be set, and a few
other pieces of information.
The runtime configuration editor for a Local Camel Context runtime profile contains the following tabs:
Camel Context File—specifies the full path the context file containing your routes.
Main—specifies the project, the fully qualified name of the main class to invoke, and a few options for locating the main class.
Arguments—specifies the command line arguments used when starting the JVM.
JRE—specifies the JRE to use.
Classpath—specifies additional JARs that need to on the classpath.
Source—specifies where to locate the source files to use when running the debugger.
Environment—specifies any environment variables that need to be set.
Common—specifies how Eclipse stores the profile and displays the output.
The first time a Apache Camel route is run as a local Camel context file, Fuse IDE creates a default runtime profile for the context file that should not require editing.
The Camel Context File has a single field that specifies the full path to the context file containing your route definitions. The context file must exist in an Eclipse project in the active Eclipse workspace.
The Open Resource dialog to help you locate the desired context file. The dialog is preconfigured to search for files that contain Apache Camel routes.
button opens the EclipseBy default, the runtime profile uses the standard
org.apache.camel.spring.Main
class to bootstrap the routes. This
class loads the routes and Apache Camel into a Spring container.
You can specify an alternate main class by editing the Main class field on the Main tab.
By default the only command line option passed to the JVM is:
-fa context-file
If you are using a custom main class you may need to pass in different options. To do so edit the Program arguments field on the Commands tab.
To change the VM specific arguments edit the VM arguments field on the Commands tab.
By default the classpath is set up to contain the core JARs required to run Apache Camel in a Spring container.
It does not contain any of the addition
component JARs. If your route uses components that are not part of camel-core
,
you will need to add the JARs to the table on the Classpath tab.
By default, the output from the route execution is sent to an Eclipse Console view. It can, however, be redirected to a file if needed.
To redirect the output to a file:
Select the Common tab.
Check the box next to the File: field.
Enter the path to the file where the output will be redirected.
The
, , and buttons can help you build the path to the output file.