commits@camel.apache.org Archives

Tutorial-Example-ReportIncident-Part1

Page commented by Aaron Junod

In Implementing the ReportIncidentEndpoint : running mvn compile did not create the java or package folders, or the .java file. I used the .zip as a template and created the folders and file manually.

When adding env variable had to be surrounded in quotes. added following to ~/.bash_profile (osx)
export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=128m -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005"

Change Notification Preferences

View Online | Reply To This

Description	Download Link	PGP Signature file of download
Windows Distribution	apache-camel-2.2.0.zip	apache-camel-2.2.0.zip.asc
Unix/Linux/Cygwin Distribution	apache-camel-2.2.0.tar.gz	apache-camel-2.2.0.tar.gz.asc

Description	Download Link	PGP Signature file of download
Windows Distribution	apache-camel-2.2.0.zip	apache-camel-2.2.0.zip.asc
Unix/Linux/Cygwin Distribution	apache-camel-2.2.0.tar.gz	apache-camel-2.2.0.tar.gz.asc

Name	Default Value	Description
`password`	`password`	Specifies the password to use to log in to the SMSC.
`systemType`	`cp`	This parameter is used to categorize the type of ESME (External Short Message Entity) that is binding to the SMSC (max. 13 characters).
`encoding`	`ISO-8859-1`	Defines the encoding scheme of the short message user data.
`enquireLinkTimer`	`5000`	Defines the interval in milliseconds between the confidence checks. The confidence check is used to test the communication path between an ESME and an SMSC.
`transactionTimer`	`10000`	Defines the maximum period of inactivity allowed after a transaction, after which an SMPP entity may assume that the session is no longer active. This timer may be active on either communicating SMPP entity (i.e. SMSC or ESME).
`registeredDelivery`	`1`	Is used to request an SMSC delivery receipt and/or SME originated acknowledgements. The following values are defined: `0`: No SMSC delivery receipt requested. `1`: SMSC delivery receipt requested where final delivery outcome is success or failure. `2`: SMSC delivery receipt requested where the final delivery outcome is delivery failure.
`serviceType`	`CMT`	The service type parameter can be used to indicate the SMS Application service associated with the message. The following generic service_types are defined: `CMT`: Cellular Messaging `CPT`: Cellular Paging `VMN`: Voice Mail Notification `VMA`: Voice Mail Alerting `WAP`: Wireless Application Protocol `USSD`: Unstructured Supplementary Services Data
`sourceAddr`	`1616`	Defines the address of SME (Short Message Entity) which originated this message.
`destAddr`	`1717`	Defines the destination SME address. For mobile terminated messages, this is the directory number of the recipient MS.
`sourceAddrTon`	`0`	Defines the type of number (TON) to be used in the SME originator address parameters. The following TON values are defined: `0`: Unknown `1`: International `2`: National `3`: Network Specific `4`: Subscriber Number `5`: Alphanumeric `6`: Abbreviated
`destAddrTon`	`0`	Defines the type of number (TON) to be used in the SME destination address parameters. The following TON values are defined: `0`: Unknown `1`: International `2`: National `3`: Network Specific `4`: Subscriber Number `5`: Alphanumeric `6`: Abbreviated
`sourceAddrNpi`	`0`	Defines the numeric plan indicator (NPI) to be used in the SME originator address parameters. The following NPI values are defined: `0`: Unknown `1`: ISDN (E163/E164) `2`: Data (X.121) `3`: Telex (F.69) `6`: Land Mobile (E.212) `8`: National `9`: Private `10`: ERMES `13`: Internet (IP) `18`: WAP Client Id (to be defined by WAP Forum)
`destAddrNpi`	`0`	Defines the numeric plan indicator (NPI) to be used in the SME destination address parameters. The following NPI values are defined: `0`: Unknown `1`: ISDN (E163/E164) `2`: Data (X.121) `3`: Telex (F.69) `6`: Land Mobile (E.212) `8`: National `9`: Private `10`: ERMES `13`: Internet (IP) `18`: WAP Client Id (to be defined by WAP Forum)
`priorityFlag`	`1`	Allows the originating SME to assign a priority level to the short message. Four Priority Levels are supported: `0`: Level 0 (lowest) priority `1`: Level 1 priority `2`: Level 2 priority `3`: Level 3 (highest) priority
`replaceIfPresentFlag`	`0`	Used to request the SMSC to replace a previously submitted message, that is still pending delivery. The SMSC will replace an existing message provided that the source address, destination address and service type match the same fields in the new message. The following replace if present flag values are defined: `0`: Don't replace `1`: Replace
`typeOfNumber`	`0`	Defines the type of number (TON) to be used in the SME. The following TON values are defined: `0`: Unknown `1`: International `2`: National `3`: Network Specific `4`: Subscriber Number `5`: Alphanumeric `6`: Abbreviated
`numberingPlanIndicator`	`0`	Defines the numeric plan indicator (NPI) to be used in the SME. The following NPI values are defined: `0`: Unknown `1`: ISDN (E163/E164) `2`: Data (X.121) `3`: Telex (F.69) `6`: Land Mobile (E.212) `8`: National `9`: Private `10`: ERMES `13`: Internet (IP) `18`: WAP Client Id (to be defined by WAP Forum)

Header	Description
`CamelSmppDestAddr`	Defines the destination SME address. For mobile terminated messages, this is the directory number of the recipient MS.
`CamelSmppDestAddrTon`	Defines the type of number (TON) to be used in the SME destination address parameters. The following TON values are defined: `0`: Unknown `1`: International `2`: National `3`: Network Specific `4`: Subscriber Number `5`: Alphanumeric `6`: Abbreviated
`CamelSmppDestAddrNpi`	Defines the numeric plan indicator (NPI) to be used in the SME destination address parameters. The following NPI values are defined: `0`: Unknown `1`: ISDN (E163/E164) `2`: Data (X.121) `3`: Telex (F.69) `6`: Land Mobile (E.212) `8`: National `9`: Private `10`: ERMES `13`: Internet (IP) `18`: WAP Client Id (to be defined by WAP Forum)
`CamelSmppSourceAddr`	Defines the address of SME (Short Message Entity) which originated this message.
`CamelSmppSourceAddrTon`	Defines the type of number (TON) to be used in the SME originator address parameters. The following TON values are defined: `0`: Unknown `1`: International `2`: National `3`: Network Specific `4`: Subscriber Number `5`: Alphanumeric `6`: Abbreviated
`CamelSmppSourceAddrNpi`	Defines the numeric plan indicator (NPI) to be used in the SME originator address parameters. The following NPI values are defined: `0`: Unknown `1`: ISDN (E163/E164) `2`: Data (X.121) `3`: Telex (F.69) `6`: Land Mobile (E.212) `8`: National `9`: Private `10`: ERMES `13`: Internet (IP) `18`: WAP Client Id (to be defined by WAP Forum)
`CamelSmppServiceType`	The service type parameter can be used to indicate the SMS Application service associated with the message. The following generic service_types are defined: `CMT`: Cellular Messaging `CPT`: Cellular Paging `VMN`: Voice Mail Notification `VMA`: Voice Mail Alerting `WAP`: Wireless Application Protocol `USSD`: Unstructured Supplementary Services Data
`CamelSmppRegisteredDelivery`	Is used to request an SMSC delivery receipt and/or SME originated acknowledgements. The following values are defined: `0`: No SMSC delivery receipt requested. `1`: SMSC delivery receipt requested where final delivery outcome is success or failure. `2`: SMSC delivery receipt requested where the final delivery outcome is delivery failure.
`CamelSmppPriorityFlag`	Allows the originating SME to assign a priority level to the short message. Four Priority Levels are supported: `0`: Level 0 (lowest) priority `1`: Level 1 priority `2`: Level 2 priority `3`: Level 3 (highest) priority
`CamelSmppScheduleDeliveryTime`	This parameter specifies the scheduled time at which the message delivery should be first attempted. It defines either the absolute date and time or relative time from the current SMSC time at which delivery of this message will be attempted by the SMSC. It can be specified in either absolute time format or relative time format. The encoding of a time format is specified in chapter 7.1.1. in the smpp specification v3.4.
`CamelSmppValidityPeriod`	The validity period parameter indicates the SMSC expiration time, after which the message should be discarded if not delivered to the destination. It can be defined in absolute time format or relative time format. The encoding of absolute and relative time format is specified in chapter 7.1.1 in the smpp specification v3.4.
`CamelSmppReplaceIfPresentFlag`	The replace if present flag parameter is used to request the SMSC to replace a previously submitted message, that is still pending delivery. The SMSC will replace an existing message provided that the source address, destination address and service type match the same fields in the new message. The following values are defined: `0`: Don't replace `1`: Replace

Header	Description
`CamelSmppSequenceNumber`	only for alert notification and deliver sm: A sequence number allows a response PDU to be correlated with a request PDU. The associated SMPP response PDU must preserve this field.
`CamelSmppCommandId`	only for alert notification and deliver sm: The command id field identifies the particular SMPP PDU. For the complete list of defined values see chapter 5.1.2.1 in the smpp specification v3.4.
`CamelSmppSourceAddr`	only for alert notification and deliver sm: Defines the address of SME (Short Message Entity) which originated this message.
`CamelSmppSourceAddrNpi`	only for alert notification: Defines the numeric plan indicator (NPI) to be used in the SME originator address parameters. The following NPI values are defined: `0`: Unknown `1`: ISDN (E163/E164) `2`: Data (X.121) `3`: Telex (F.69) `6`: Land Mobile (E.212) `8`: National `9`: Private `10`: ERMES `13`: Internet (IP) `18`: WAP Client Id (to be defined by WAP Forum)
`CamelSmppSourceAddrTon`	only for alert notification: Defines the type of number (TON) to be used in the SME originator address parameters. The following TON values are defined: `0`: Unknown `1`: International `2`: National `3`: Network Specific `4`: Subscriber Number `5`: Alphanumeric `6`: Abbreviated
`CamelSmppEsmeAddr`	only for alert notification: Defines the destination ESME address. For mobile terminated messages, this is the directory number of the recipient MS.
`CamelSmppEsmeAddrNpi`	only for alert notification: Defines the numeric plan indicator (NPI) to be used in the ESME originator address parameters. The following NPI values are defined: `0`: Unknown `1`: ISDN (E163/E164) `2`: Data (X.121) `3`: Telex (F.69) `6`: Land Mobile (E.212) `8`: National `9`: Private `10`: ERMES `13`: Internet (IP) `18`: WAP Client Id (to be defined by WAP Forum)
`CamelSmppEsmeAddrTon`	only for alert notification: Defines the type of number (TON) to be used in the ESME originator address parameters. The following TON values are defined: `0`: Unknown `1`: International `2`: National `3`: Network Specific `4`: Subscriber Number `5`: Alphanumeric `6`: Abbreviated
`CamelSmppId`	only for smsc delivery receipt: The message ID allocated to the message by the SMSC when originally submitted.
`CamelSmppDelivered`	only for smsc delivery receipt: Number of short messages delivered. This is only relevant where the original message was submitted to a distribution list.The value is padded with leading zeros if necessary.
`CamelSmppDoneDate`	only for smsc delivery receipt: The time and date at which the short message reached it's final state. The format is as follows: YYMMDDhhmm.
`CamelSmppStatus`	only for smsc delivery receipt: The final status of the message. The following values are defined: `DELIVRD`: Message is delivered to destination `EXPIRED`: Message validity period has expired. `DELETED`: Message has been deleted. `UNDELIV`: Message is undeliverable `ACCEPTD`: Message is in accepted state (i.e. has been manually read on behalf of the subscriber by customer service) `UNKNOWN`: Message is in invalid state `REJECTD`: Message is in a rejected state
`CamelSmppError`	only for smsc delivery receipt: Where appropriate this may hold a Network specific error code or an SMSC error code for the attempted delivery of the message. These errors are Network or SMSC specific and are not included here.
`CamelSmppSubmitDate`	only for smsc delivery receipt: The time and date at which the short message was submitted. In the case of a message which has been replaced, this is the date that the original message was replaced. The format is as follows: YYMMDDhhmm.
`CamelSmppSubmitted`	only for smsc delivery receipt: Number of short messages originally submitted. This is only relevant when the original message was submitted to a distribution list.The value is padded with leading zeros if necessary.
`CamelSmppDestAddr`	only for deliver sm: Defines the destination SME address. For mobile terminated messages, this is the directory number of the recipient MS.
`CamelSmppScheduleDeliveryTime`	only for deliver sm: This parameter specifies the scheduled time at which the message delivery should be first attempted. It defines either the absolute date and time or relative time from the current SMSC time at which delivery of this message will be attempted by the SMSC. It can be specified in either absolute time format or relative time format. The encoding of a time format is specified in Section 7.1.1. in the smpp specification v3.4.
`CamelSmppValidityPeriod`	only for deliver sm: The validity period parameter indicates the SMSC expiration time, after which the message should be discarded if not delivered to the destination. It can be defined in absolute time format or relative time format. The encoding of absolute and relative time format is specified in Section 7.1.1 in the smpp specification v3.4.

Component / ArtifactId / URI	Description
ActiveMQ / activemq-camel activemq:[topic:]destinationName	For JMS Messaging with Apache ActiveMQ
ActiveMQ Journal / activemq-core activemq.journal:directory-on-filesystem	Uses ActiveMQ's fast disk journaling implementation to store message bodies in a rolling log file
AMQP / camel-amqp amqp:[topic:]destinationName	For Messaging with AMQP protocol
Atom / camel-atom atom:uri	Working with Apache Abdera for atom integration, such as consuming an atom feed.
Bean / camel-core bean:beanName[?method=someMethod]	Uses the Bean Binding to bind message exchanges to beans in the Registry. Is also used for exposing and invoking POJO (Plain Old Java Objects).
Browse / camel-core browse:someName	Provdes a simple BrowsableEndpoint which can be useful for testing, visualisation tools or debugging. The exchanges sent to the endpoint are all available to be browsed.
Cache / camel-cache cache://cachename[?options]	The cache component facilitates creation of caching endpoints and processors using EHCache as the cache implementation.
Cometd / camel-cometd cometd://host:port/channelname	Used to deliver messages using the jetty cometd implementation of the bayeux protocol
CXF / camel-cxf cxf:address[?serviceClass=...]	Working with Apache CXF for web services integration
CXFRS / camel-cxf cxfrs:address[?resourcesClasses=...]	Working with Apache CXF for REST services integration
DataSet / camel-core dataset:name	For load & soak testing the DataSet provides a way to create huge numbers of messages for sending to Components or asserting that they are consumed correctly
Direct / camel-core direct:name	Synchronous call to another endpoint
Esper / camel-esper in camel-extra esper:name	Working with the Esper Library for Event Stream Processing
Event / camel-spring event://default spring-event://default	Working with Spring ApplicationEvents
File / camel-core file://nameOfFileOrDirectory	Sending messages to a file or polling a file or directory. Camel 1.x use this link File.
Flatpack / camel-flatpack flatpack:[fixed\|delim]:configFile	Processing fixed width or delimited files or messages using the FlatPack library
Freemarker / camel-freemarker freemarker:someTemplateResource	Generates a response using a Freemarker template
FTP / camel-ftp ftp://host[:port]/fileName	Sending and receiving files over FTP. Camel 1.x use this link FTP.
FTPS / camel-ftp ftps://host[:port]/fileName	Sending and receiving files over FTP Secure (TLS and SSL).
GHttp / camel-gae ghttp://hostname[:port][/path][?options] ghttp:///path[?options]	Provides connectivity to the URL fetch service of Google App Engine but can also be used to receive messages from servlets. See also Camel Components for Google App Engine.
GTask / camel-gae gtask://queue-name	supports asynchronous message processing on Google App Engine by using the task queueing service as message queue. See also Camel Components for Google App Engine.
GMail / camel-gae gmail://user@gmail.com[?options] gmail://user@googlemail.com[?options]	Supports sending of emails via the mail service of Google App Engine. See also Camel Components for Google App Engine.
Hibernate / camel-hibernate in camel-extra hibernate://entityName	For using a database as a queue via the Hibernate library
HL7 / camel-hl7 mina:tcp://hostname[:port]	For working with the HL7 MLLP protocol and the HL7 model using the HAPI library
HTTP / camel-http http://hostname[:port]	For calling out to external HTTP servers
iBATIS / camel-ibatis ibatis://sqlOperationName	Performs a query, poll, insert, update or delete in a relational database using Apache iBATIS
IMap / camel-mail imap://hostname[:port]	Receiving email using IMap
IRC / camel-irc irc:host[:port]/#room	For IRC communication
JavaSpace / camel-javaspace javaspace:jini://host?spaceName=mySpace?...	Sending and receiving messages through JavaSpace
JBI / servicemix-camel jbi:serviceName	For JBI integration such as working with Apache ServiceMix
JCR / camel-jcr jcr://user:password@repository/path/to/node	Storing a message in a JCR (JSR-170) compliant repository like Apache Jackrabbit
JDBC / camel-jdbc jdbc:dataSourceName?options	For performing JDBC queries and operations
Jetty / camel-jetty jetty:url	For exposing services over HTTP
JMS / camel-jms jms:[topic:]destinationName	Working with JMS providers
JPA / camel-jpa jpa://entityName	For using a database as a queue via the JPA specification for working with OpenJPA, Hibernate or TopLink
JT/400 / camel-jt400 jt400://user:pwd@system/<path_to_dtaq>	For integrating with data queues on an AS/400 (aka System i, IBM i, i5, ...) system
LDAP / camel-ldap ldap:host[:port]?base=...[&scope=<scope>]	Performing searches on LDAP servers (<scope> must be one of object\|onelevel\|subtree)
Log / camel-core log:loggingCategory[?level=ERROR]	Uses Jakarta Commons Logging to log the message exchange to some underlying logging system like log4j
Mail / camel-mail mail://user-info@host:port	Sending and receiving email
MINA / camel-mina [tcp\|udp\|multicast]:host[:port]	Working with Apache MINA
Mock / camel-core mock:name	For testing routes and mediation rules using mocks
MSV / camel-msv msv:someLocalOrRemoteResource	Validates the payload of a message using the MSV Library
Multicast / camel-mina multicast://host:port	Working with TCP protocols using Apache MINA
NMR / servicemix-nmr nmr://serviceName	Integration with the Normalized Message Router BUS in ServiceMix 4.x
POP / camel-mail pop3://user-info@host:port	Receiving email using POP3 and JavaMail
Printer / camel-printer lpr://host:port/path/to/printer[?options]	The printer component facilitates creation of printer endpoints to local, remote and wireless printers. The endpoints provide the ability to print camel directed payloads when utilized on camel routes.
Quartz / camel-quartz quartz://groupName/timerName	Provides a scheduled delivery of messages using the Quartz scheduler
Quickfix / camel-quickfix quickfix-server:config file quickfix-client:config-file	Implementation of the QuickFix for Java engine which allow to send/receive FIX messages
Ref / camel-core ref:name	Component for lookup of existing endpoints bound in the Registry.
Restlet / camel-restlet restlet:restletUrl[?options]	Component for consuming and producing Restful resources using Restlet
RMI / camel-rmi rmi://host[:port]	Working with RMI
RNC / camel-jing rnc:/relativeOrAbsoluteUri	Validates the payload of a message using RelaxNG Compact Syntax
RNG / camel-jing rng:/relativeOrAbsoluteUri	Validates the payload of a message using RelaxNG
RSS / camel-rss rss:uri	Working with ROME for RSS integration, such as consuming an RSS feed.
SEDA / camel-core seda:name	Asynchronous call to another endpoint in the same Camel Context
SERVLET / camel-servlet servlet:uri	For exposing services over HTTP through the servlet which is deployed into the Web container.
SFTP / camel-ftp sftp://host[:port]/fileName	Sending and receiving files over SFTP (FTP over SSH). Camel 1.x use this link FTP.
Smooks / camel-smooks in camel-extra unmarshal(edi)	For working with EDI parsing using the Smooks library
SMTP / camel-mail smtp://user-info@host[:port]	Sending email using SMTP and JavaMail
SMPP / camel-smpp smpp://user-info@host[:port]?options	To send and receive SMS using Short Messaging Service Center using the JSMPP library
SNMP / camel-snmp snmp://host[:port]?options	Polling OID values and receiving traps using SNMP via SNMP4J library
SpringIntegration / camel-spring-integration spring-integration:defaultChannelName	The bridge component of Camel and Spring Integration
SQL / camel-sql sql:select * from table where id=#	Performing SQL queries using JDBC
Stream / camel-stream stream:[in\|out\|err\|file]	Read or write to an input/output/error/file stream rather like unix pipes
StringTemplate / camel-stringtemplate string-template:someTemplateResource	Generates a response using a String Template
TCP / camel-mina tcp://host:port	Working with TCP protocols using Apache MINA
Test / camel-spring test:expectedMessagesEndpointUri	Creates a Mock endpoint which expects to receive all the message bodies that could be polled from the given underlying endpoint
Timer / camel-core timer://name	A timer endpoint
UDP / camel-mina udp://host:port	Working with UDP protocols using Apache MINA
Validation / camel-spring validation:someLocalOrRemoteResource	Validates the payload of a message using XML Schema and JAXP Validation
Velocity / camel-velocity velocity:someTemplateResource	Generates a response using an Apache Velocity template
VM / camel-core vm:name	Asynchronous call to another endpoint in the same JVM
XMPP / camel-xmpp xmpp://host:port/room	Working with XMPP and Jabber
XQuery / camel-saxon xquery:someXQueryResource	Generates a response using an XQuery template
XSLT / camel-spring xslt:someTemplateResource	Generates a response using an XSLT template

Type	Number of beans	Description
PackageScanClassResolver	0..1	To use a 3rd party package scan resolver. More details at Pluggable Class Resolvers.
ClassResolver	0..1	To use a 3rd party class resolver. More details at Pluggable Class Resolvers.
FactoryFinderResolver	0..1	To use a 3rd party factory finder.
Registry	0..1	To use a 3rd party bean registry. By default Camel will use Spring ApplicationContext as registry.
Debugger	0..1	To use a Debugger usually for tooling.
Tracer	0..1	To use a 3rd party Tracer.
TraceFormatter	0..1	To use a bean that has the tracing options configured.
HandleFault	0..1	To use a 3rd part fault handler to handle FAULT messages.
Delayer	0..1	To use a 3rd part Delayer.
ManagementStrategy	0..1	Camel 2.1: To use a 3rd part strategy for management, for example JMX management.
EventFactory	0..1	Camel 2.1: To use a 3rd part event factory.
EventNotifier	0..1	Camel 2.1: To use a 3rd part event notifier.
InflightRepository	0..1	Camel 2.1: To use a 3rd part inflight repository.

Type	Number of beans	Description
InterceptStrategy	0..n	To use your own Intercept that intercepts every processing steps in all routes in the CamelContext. For instance you can use this to do an AOP like performance timer interceptor.
LifecycleStrategy	0..n	Camel 2.1: To use 3rd party lifecycle strategies. By default Camel uses a JMX aware that does JMX instrumentation.

Expression	Type	File Consumer	File Producer	FTP Consumer	FTP Producer	Description
file:name	String	yes	no	yes	no	refers to the file name (is relative to the starting directory, see note below)
file:name.noext	String	yes	no	yes	no	refers to the file name with no extension (is relative to the starting directory, see note below)
file:onlyname	String	yes	no	yes	no	Camel 2.0: refers to the file name only with no leading paths.
file:onlyname.noext	String	yes	no	yes	no	Camel 2.0: refers to the file name only with no extension and with no leading paths.
file:ext	String	yes	no	yes	no	Camel 1.6.1/Camel 2.0: refers to the file extension only
file:parent	String	yes	no	yes	no	refers to the file parent
file:path	String	yes	no	yes	no	refers to the file path
file:absolute	Boolean	yes	no	no	no	Camel 2.0: refers to whether the file is regarded as absolute or relative
file:absolute.path	String	yes	no	no	no	refers to the absolute file path
file:length	Long	yes	no	yes	no	refers to the file length returned as a Long type
file:modified	Date	yes	no	yes	no	Camel 2.0: refers to the file last modified returned as a Date type
date:command:pattern	String	yes	yes	yes	yes	for date formatting using the `java.text.SimepleDataFormat` patterns. Is an extension to the Simple language. Additional command is: file (consumers only) for the last modified timestamp of the file. Notice: all the commands from the Simple language can also be used.

Expression	Returns
file:name	test\hello.txt
file:name.noext	test\hello
file:onlyname	hello.txt
file:onlyname.noext	hello
file:ext	txt
file:parent	filelanguage\test
file:path	filelanguage\test\hello.txt
file:absolute	false
file:absolute.path	\workspace\camel\camel-core\target\filelanguage\test\hello.txt

Variable	Type	Description
id	String	the input message id
body	Object	the input body
in.body	Object	the input body
out.body	Object	the output body
header.foo	Object	refer to the input foo header
headers.foo	Object	refer to the input foo header
in.header.foo	Object	refer to the input foo header
in.headers.foo	Object	refer to the input foo header
out.header.foo	Object	refer to the out header foo
out.headers.foo	Object	refer to the out header foo
property.foo	Object	refer to the foo property on the exchange
sys.foo	String	refer to the system property
exception.message	String	New in Camel 2.0. Refer to the exception.messsage on the exchange, is null if no exception set on exchange
date:command:pattern	String	New in Camel 1.5. Date formatting using the `java.text.SimepleDataFormat` patterns. Supported commands are: now for current timestamp, in.header.xxx or header.xxx to use the Date object in the IN header with the key xxx. out.header.xxx to use the Date object in the OUT header with the key xxx.
bean:bean expression	Object	New in Camel 1.5. Invoking a bean expression using the Bean language. Specifying a method name you must use dot as separator. In Camel 2.0 we also support the ?method=methodname syntax that is used by the Bean component.

Operator	Description
==	equals
>	greather than
>=	greather than or equals
<	less than
<=	less than or equals
!=	not equals
contains	For testing if contains in a string based value
not contains	For testinf if not contains in a string based value
regex	For matching against a given regular expression pattern defined as a String value
not regex	For not matching against a given regular expression pattern defined as a String value
in	For matching if in a set of values, each element must be separated by comma.
not in	For matching if not in a set of values, each element must be separated by comma.
is	For matching if the left hand side type is an instanceof the value.
not is	For matching if the left hand side type is not an instanceof the value.
range	For matching if the left hand side is within a range of values defined as numbers: `from..to`
not range	For matching if the left hand side is not within a range of values defined as numbers: `from..to`

Operator	Description
and	and is used to group two expressions
or	or is used to group two expressions

Spring property	System property	Default Value	Description
id			The JMX agent name, and it is not optional
usePlatformMBeanServer	org.apache.camel.jmx.usePlatformMBeanServer	false, true - Release 1.5 or later	If true then it will use the plateform MBean server form the JVM
mbeanServerDefaultDomain	org.apache.camel.jmx.mbeanServerDefaultDomain	org.apache.camel	The default JMX domain of the MBeanServer
mbeanObjectDomainName	org.apache.camel.jmx.mbeanObjectDomainName	org.apache.camel	The JMX domain that all objects names will use
createConnector	org.apache.camel.jmx.createRmiConnect	false	If we should create a JMX connector (to allow remote management) for the MBeanServer
registryPort	org.apache.camel.jmx.rmiConnector.registryPort	1099	The port that the JMX RMI registry will use
connectorPort	org.apache.camel.jmx.rmiConnector.connectorPort	-1 (dynamic)	The port that the JMX RMI server will use
serviceUrlPath	org.apache.camel.jmx.serviceUrlPath	/jmxrmi/camel	The path that JMX connector will be registered under
onlyRegisterProcessorWithCustomId	org.apache.camel.jmx.onlyRegisterProcessorWithCustomId	false	Camel 2.0: If this option is enabled then only processors with a custom id set will be registered. This allows you to filer out unwanted processors in the JMX console.
statisticsLevel		`All`	Camel 2.1: Configures the level for whether performance statistics is enabled for the mbean. See section Configuring level of granularity for performance statistics for more details.

Type	MBean wrapper
CamelContext	ManagedCamelContext
Component	ManagedComponent
Endpoint	ManagedEndpoint
Consumer	ManagedConsumer
Producer	ManagedProducer
Route	ManagedRoute
Processor	ManagedProcessor
Tracer	ManagedTracer
Service	ManagedService

Type	MBean wrapper
ScheduledPollConsumer	ManagedScheduledPollConsumer
BrowsableEndpoint	ManagedBrowseableEndpoint
Throttler	ManagedThrottler
Delayer	ManagedDelayer
SendProcessor	ManagedSendProcessor

Name	Default Value	Description
`password`	`null`	Specifies the password to use to log in to the remote file system.
`binary`	`false`	Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (`false`).
`localWorkDirectory`	`null`	When consuming, a local work directory can be used to store the remote file content directly in local files, to avoid loading the content into memory. This is beneficial, if you consume a very big remote file and thus can conserve memory. See below for more details.
`passiveMode`	`false`	FTP and FTPS only: Specifies whether to use passive mode connections. Default is active mode (`false`).
`securityProtocol`	`TLS`	FTPS only: Sets the underlying security protocol. The following values are defined: `TLS`: Transport Layer Security `SSL`: Secure Sockets Layer
`isImplicit`	`false`	FTPS only: Sets the security mode(implicit/explicit). Default is explicit (`false`).
`knownHostsFile`	`null`	SFTP only: Sets the `known_hosts` file, so that the SFTP endpoint can do host key verification.
`privateKeyFile`	`null`	SFTP only: Set the private key file to that the SFTP endpoint can do private key verification.
`privateKeyFilePassphrase`	`null`	SFTP only: Set the private key file passphrase to that the SFTP endpoint can do private key verification.
`maximumReconnectAttempts`	3	Specifies the maximum reconnect attempts Camel performs when it tries to connect to the remote FTP server. Use 0 to disable this behavior.
`reconnectDelay`	1000	Delay in millis Camel will wait before performing a reconnect attempt.
`ftpClient`	`null`	FTP and FTPS Only: Camel 2.1: Allows you to use a custom `org.apache.commons.net.ftp.FTPClient` instance.
`ftpClientConfig`	`null`	FTP and FTPS Only: Camel 2.1: Allows you to use a custom `org.apache.commons.net.ftp.FTPClientConfig` instance.
`ftpClient.trustStore.file`	`null`	FTPS Only: Sets the trust store file, so that the FTPS client can look up for trusted certificates.
`ftpClient.trustStore.type`	`JKS`	FTPS Only: Sets the trust store type.
`ftpClient.trustStore.algorithm`	`SunX509`	FTPS Only: Sets the trust store algorithm.
`ftpClient.trustStore.password`	`null`	FTPS Only: Sets the trust store password.
`ftpClient.keyStore.file`	`null`	FTPS Only: Sets the key store file, so that the FTPS client can look up for the private certificate.
`ftpClient.keyStore.type`	`JKS`	FTPS Only: Sets the key store type.
`ftpClient.keyStore.algorithm`	`SunX509`	FTPS Only: Sets the key store algorithm.
`ftpClient.keyStore.password`	`null`	FTPS Only: Sets the key store password.
`ftpClient.keyStore.keyPassword`	`null`	FTPS Only: Sets the private key password.

Header	Description
`CamelFileName`	Specifies the output file name (relative to the endpoint directory) to be used for the output message when sending to the endpoint. If this is not present and no expression either, then a generated message ID is used as the filename instead.
`CamelFileNameProduced`	The actual absolute filepath (path + name) for the output file that was written. This header is set by Camel and its purpose is providing end-users the name of the file that was written.
`CamelFileBatchIndex`	Current index out of total number of files being consumed in this batch.
`CamelFileBatchSize`	Total number of files being consumed in this batch.
`CamelFileHost`	The remote hostname.
`CamelFileLocalWorkPath`	Path to the local work file, if local work directory is used.

commits@camel.apache.org Archives

[CONF] Apache Camel > Tutorial-Example-ReportIncident-Part1

Page commented by Aaron Junod

svn commit: r888938 - /camel/trunk/components/camel-ftp/src/test/java/org/apache/camel/component/file/remote/FtpConsumerLocalWorkDirectoryAsAbsolutePathTest.java

svn commit: r888857 - in /camel/trunk/examples/camel-example-etl/src/main/resources/META-INF: LICENSE.txt NOTICE.txt persistence.xml spring/

svn commit: r888856 - in /camel/trunk/examples/camel-example-etl: ./ src/main/java/org/apache/camel/example/etl/ src/main/resources/ src/profiles/eclipselink/ src/profiles/eclipselink/META-INF/ src/profiles/eclipselink/META-INF/spring/ src/profiles/hib...

[CONF] Apache Camel > Tutorial-Example-ReportIncident-Part1

Page commented by Aaron Junod

svn commit: r888843 - /camel/trunk/components/camel-jpa/src/main/java/org/apache/camel/component/jpa/JpaConsumer.java

svn commit: r888834 - /camel/trunk/components/camel-jpa/src/main/java/org/apache/camel/component/jpa/JpaConsumer.java

svn commit: r888810 - in /camel/trunk/components/camel-ftp/src/test/java/org/apache/camel/component/file/remote: FtpConsumerLocalWorkDirectoryAsAbsolutePathTest.java FtpConsumerLocalWorkDirectoryTest.java

svn commit: r888798 - /camel/trunk/camel-core/pom.xml

svn commit: r888797 - /camel/trunk/camel-core/src/test/java/org/apache/camel/issues/CBRContainsIssueTest.java

svn commit: r888774 - /camel/trunk/components/camel-jms/src/test/java/org/apache/camel/component/jms/JmsRouteEndpointTest.java

svn commit: r888734 - in /camel/trunk: camel-core/src/test/java/org/apache/camel/management/ components/camel-atom/src/test/java/org/apache/camel/component/atom/ components/camel-cxf/src/test/java/org/apache/camel/component/cxf/jaxrs/ components/camel-...

Hello

Hello

svn commit: r888729 - in /camel/trunk: parent/ tests/camel-itest-karaf/ tests/camel-itest-osgi/ tests/camel-itest-osgi/src/test/java/org/apache/camel/itest/osgi/ tests/camel-itest-osgi/src/test/java/org/apache/camel/itest/osgi/jaxb/ tests/camel-itest-o...

[CONF] Apache Camel > Articles

Page edited by Claus Ibsen

Articles on Apache Camel

Webinar or Video presentations on Camel

Podcasts where Camel is taking part

Books on Apache Camel

Camel bloggers

svn commit: r888719 - in /camel/trunk/camel-core/src: main/java/org/apache/camel/model/CatchDefinition.java test/java/org/apache/camel/processor/TryCatchMustHaveExceptionConfiguredTest.java

svn commit: r888709 - in /camel/trunk/components/camel-ftp/src: main/java/org/apache/camel/component/file/remote/ test/java/org/apache/camel/component/file/remote/

svn commit: r888706 - /camel/trunk/camel-core/src/test/java/org/apache/camel/processor/TryCatchContinueToRouteTest.java

[CONF] Apache Camel > Camel 2.2.0 Release

Page edited by Christian Mueller

Camel 2.2.0 release (currently in progress)

New and Noteworthy

New Enterprise Integration Patterns

New Components

New DSL

New Annotations

New Data Formats

New Languages

New Examples

API breaking

Known Issues

Important changes to consider when upgrading

Spring jar dependencies have been cut down in camel-core.

Getting the Distributions

Binary Distributions

Source Distributions

Getting the Binaries using Maven 2

SVN Tag Checkout

Changelog

[CONF] Apache Camel > Camel 2.2.0 Release

Page edited by Christian Mueller

Camel 2.2.0 release (currently in progress)

New and Noteworthy

New Enterprise Integration Patterns

New Components

New DSL

New Annotations

New Data Formats

New Languages

New Examples

API breaking

Known Issues

Important changes to consider when upgrading

Spring jar dependencies have been cut down in camel-core.

Getting the Distributions

Binary Distributions

Source Distributions

Getting the Binaries using Maven 2

SVN Tag Checkout

Changelog

svn commit: r888432 - in /camel/trunk/components/camel-ftp/src/test/java/org/apache/camel/component/file/remote: FtpConsumerLocalWorkDirectoryAsAbsolutePathTest.java FtpConsumerLocalWorkDirectoryTest.java

svn commit: r888416 - in /camel/trunk/components/camel-jcr/src/test/java/org/apache/camel/component/jcr: JcrAuthTestBase.java JcrNodePathCreationTest.java JcrRouteTest.java

svn commit: r888384 - in /camel/trunk/examples/camel-example-etl: ./ src/main/java/org/apache/camel/example/etl/ src/main/resources/META-INF/ src/main/resources/META-INF/spring/ src/profiles/ src/profiles/openjpa/ src/profiles/openjpa/META-INF/ src/pro...

[CONF] Apache Camel > SMPP

Page edited by Claus Ibsen

SMPP Component

URI format

URI Options

Message Headers

Samples