From commits-return-39314-apmail-camel-commits-archive=camel.apache.org@camel.apache.org Thu Feb 5 11:20:13 2015 Return-Path: X-Original-To: apmail-camel-commits-archive@www.apache.org Delivered-To: apmail-camel-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5534B17666 for ; Thu, 5 Feb 2015 11:20:13 +0000 (UTC) Received: (qmail 78896 invoked by uid 500); 5 Feb 2015 11:20:13 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 78836 invoked by uid 500); 5 Feb 2015 11:20:13 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 78827 invoked by uid 99); 5 Feb 2015 11:20:13 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Feb 2015 11:20:13 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id B1EA0AC0044 for ; Thu, 5 Feb 2015 11:20:12 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r939072 [1/2] - in /websites/production/camel/content: book-in-one-page.html book-languages-appendix.html cache/main.pageCache simple.html Date: Thu, 05 Feb 2015 11:20:12 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150205112012.B1EA0AC0044@hades.apache.org> Author: buildbot Date: Thu Feb 5 11:20:11 2015 New Revision: 939072 Log: Production update by buildbot for camel Modified: websites/production/camel/content/book-in-one-page.html websites/production/camel/content/book-languages-appendix.html websites/production/camel/content/cache/main.pageCache websites/production/camel/content/simple.html Modified: websites/production/camel/content/book-in-one-page.html ============================================================================== --- websites/production/camel/content/book-in-one-page.html (original) +++ websites/production/camel/content/book-in-one-page.html Thu Feb 5 11:20:11 2015 @@ -4121,11 +4121,11 @@ While not actual tutorials you might fin

Preface

This tutorial aims to guide the reader through the stages of creating a project which uses Camel to facilitate the routing of messages from a JMS queue to a Spring service. The route works in a synchronous fashion returning a response to the client.

+/*]]>*/

  • Tutorial on Spring Remoting with JMS
  • Preface
  • Prerequisites
  • Distribution
  • About
  • Create the Camel Project
  • Writing the Server @@ -6311,11 +6311,11 @@ So we completed the last piece in the pi
    +/*]]>*/
    • Tutorial using Axis 1.4 with Apache Camel
      • Prerequisites
      • Distribution
      • Introduction
      • Setting up the project to run Axis @@ -8860,7 +8860,7 @@ result = body * 2 + 1

        The Simple language have been improved from Camel 2.9 onwards to use a better syntax parser, which can do index precise error messages, so you know exactly what is wrong and where the problem is. For example if you have made a typo in one of the operators, then previously the parser would not be able to detect this, and cause the evaluation to be true. There is a few changes in the syntax which are no longer backwards compatible. When using Simple language as a Predicate then the literal text must be enclosed in either single or double quotes. For example: "${body} == 'Camel'". Notice how we have single quotes around the literal. The old style of using "body" and "header.foo" to refer to the message body and header is @deprecated, and its encouraged to always use ${ } tokens for the built-in functions.
        The range operator now requires the range to be in single quote as well as shown: "${header.zip} between '30000..39999'".

    -

    To get the body of the in message: "body", or "in.body" or "${body}".

    A complex expression must use ${ } placeholders, such as: "Hello ${in.header.name} how are you?".

    You can have multiple functions in the same expression: "Hello ${in.header.name} this is ${in.header.me} speaking".
    However you can not nest functions in Camel 2.8.x or older (i.e. having another ${ } placeholder in an existing, is not allowed).
    From Camel 2.9 onwards you can nest functions.

    Variables

    Variable

    Type

    Description

    camelId

    String

    Camel 2.10: the CamelContext name

    camelContext.OGNL

    Object

    Camel 2.11: the CamelContext invoked using a Camel OGNL expression.

    exchangeId

    String

    Camel 2.3: the exchange id

    id

    String

    the input message id

    body

    Object

    the input body

    in.body

    Object

    the input body

    body.OGNL

    Object

    Camel 2.3: the input body invoked using a Camel OGNL expression.

    in.body.OGNL

    Object

    Camel 2.3: the input body invoked using a Camel OGNL expression.

    bodyAs(type)

    Type

    Camel 2.3: Converts the body to the given type determined by its classname. The converted body can be null.

    mandatoryBodyAs(type)

    Type

    Camel 2.5: Converts the body to the given type determined by its classname, and expects the body to be not null.

    out.body

    Object

    the output body

    header.foo

    Object

    refer to the input foo header

    header[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    headers.foo

    Object

    refer to the input foo header

    headers[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    in.header.foo

    Object

    refer to the input foo header

    in.header[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    in.headers.foo

    Object

    refer to the input foo header

    in.headers[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    header.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lookup on the map with bar as key

    in.header.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lookup on the map with bar as key

    in.headers.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lo okup on the map with bar as key

    header.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    in.header.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    in.headers.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    out.header.foo

    Object

    refer to the out header foo

    out.header[foo]

    Object

    Camel 2.9.2: refer to the out header foo

    out.headers.foo

    Object

    refer to the out header foo

    out.headers[foo]

    Object

    Camel 2.9.2: refer to the out header foo

    headerAs(key,type)

    Type

    Camel 2.5: Converts the header to the given type determined by its classname

    headers

    Map

    Camel 2.9: refer to the input headers

    in.headers

    Map

    Camel 2.9: refer to the input headers

    proper ty.foo

    Object

    refer to the foo property on the exchange

    property[foo]

    Object

    Camel 2.9.2: refer to the foo property on the exchange

    property.foo.OGNL

    Object

    Camel 2.8: refer to the foo property on the exchange and invoke its value using a Camel OGNL expression.

    sys.foo

    String

    refer to the system property

    sysenv.foo

    String

    Camel 2.3: refer to the system environment

    exception

    Object

    Camel 2.4: Refer to the exception object on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    exception.OGNL

    Object

    C amel 2.4: Refer to the exchange exception invoked using a Camel OGNL expression object

    exception.message

    String

    Refer to the exception.message on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    exception.stacktrace

    String

    Camel 2.6. Refer to the exception.stracktrace on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    date:command:pattern

    String

    Date formatting using the java.text.SimpleDataFormat 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

    Invoking a bean expression using the Bean language. Specifying a method name you must use dot as separator. We also support the ?method=methodname syntax that is use d by the Bean component.

    properties:locations:key

    String

    Deprecated (use properties-location instead) Camel 2.3: Lookup a property with the given key. The locations option is optional. See more at Using PropertyPlaceholder.

    properties-location:locations:key

    String

    Camel 2.14.1: Lookup a property with the given key. The locations option is optional. See more at Using PropertyPlaceholder.

    properties:key:defaultStringCamel 2.14.1: Lookup a property with the given key. If the key does not exists or has no value, then an optional default value can be specified.

    routeId

    String

    Camel 2.11: Returns the id of the current route the Exchange is being routed.

    threadName

    String

    Camel 2.3: Returns the name of the current thread. Can be used for logging purpose.

    ref:xxx

    Object

    Camel 2.6: To lookup a bean from the Registry with the given id.

    type:name.field

    Object

    Camel 2.11: To refer to a type or field by its FQN name. To refer to a field you can append .FIELD_NAME. For example you can refer to the constant field from Exchange as: org.apache.camel.Exchange.FILE_NAME

    .

    null

     

    Camel 2.12.3: represents a null

    OGNL expression support

    Available as of Camel 2.3

    +

    To get the body of the in message: "body", or "in.body" or "${body}".

    A complex expression must use ${ } placeholders, such as: "Hello ${in.header.name} how are you?".

    You can have multiple functions in the same expression: "Hello ${in.header.name} this is ${in.header.me} speaking".
    However you can not nest functions in Camel 2.8.x or older (i.e. having another ${ } placeholder in an existing, is not allowed).
    From Camel 2.9 onwards you can nest functions.

    Variables

    Variable

    Type

    Description

    camelId

    String

    Camel 2.10: the CamelContext name

    camelContext.OGNL

    Object

    Camel 2.11: the CamelContext invoked using a Camel OGNL expression.

    exchangeId

    String

    Camel 2.3: the exchange id

    id

    String

    the input message id

    body

    Object

    the input body

    in.body

    Object

    the input body

    body.OGNL

    Object

    Camel 2.3: the input body invoked using a Camel OGNL expression.

    in.body.OGNL

    Object

    Camel 2.3: the input body invoked using a Camel OGNL expression.

    bodyAs(type)

    Type

    Camel 2.3: Converts the body to the given type determined by its classname. The converted body can be null.

    mandatoryBodyAs(type)

    Type

    Camel 2.5: Converts the body to the given type determined by its classname, and expects the body to be not null.

    out.body

    Object

    the output body

    header.foo

    Object

    refer to the input foo header

    header[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    headers.foo

    Object

    refer to the input foo header

    headers[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    in.header.foo

    Object

    refer to the input foo header

    in.header[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    in.headers.foo

    Object

    refer to the input foo header

    in.headers[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    header.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lookup on the map with bar as key

    in.header.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lookup on the map with bar as key

    in.headers.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lo okup on the map with bar as key

    header.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    in.header.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    in.headers.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    out.header.foo

    Object

    refer to the out header foo

    out.header[foo]

    Object

    Camel 2.9.2: refer to the out header foo

    out.headers.foo

    Object

    refer to the out header foo

    out.headers[foo]

    Object

    Camel 2.9.2: refer to the out header foo

    headerAs(key,type)

    Type

    Camel 2.5: Converts the header to the given type determined by its classname

    headers

    Map

    Camel 2.9: refer to the input headers

    in.headers

    Map

    Camel 2.9: refer to the input headers

    proper ty.foo

    Object

    Deprecated: refer to the foo property on the exchange

    exchangeProperty.fooObjectCamel 2.15: refer to the foo property on the exchange

    property[foo]

    Object

    Deprecated: refer to the foo property on the exchange

    exchangeProperty[foo]ObjectCamel 2.1 5: refer to the foo property on the exchange

    property.foo.OGNL

    Object

    Deprecated: refer to the foo property on the exchange and invoke its value using a Camel OGNL expression.

    exchangeProperty.foo.OGNLObjectCamel 2.15: refer to the foo property on the exchange and invoke its value using a Camel OGNL expression.

    sys.foo

    String

    refer to the system property

    sysenv.foo

    String

    Camel 2.3: refer to the system environment

    exception

    Object

    Camel 2.4: Refer to the exception object on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    exception.OGNL

    Object

    Camel 2.4: Refer to the exchange exception invoked using a Camel OGNL expression object

    exception.message

    String

    Refer to the exception.message on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    exception.stacktrace

    String

    Camel 2.6. Refer to the exception.stracktrace on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    date:command:pattern

    String

    Date formatting using the java.text.SimpleDataFormat 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

    Invoking a bean expression using the Bean language. Specifying a method name you must use dot as separator. We also support the ?method=methodname syntax that is used by the Bean component.

    properties:locations:key

    String

    Deprecated (use properties-location instead) Camel 2.3: Lookup a property with the given key. The locations option is optional. See more at Using PropertyPlaceholder.

    properties-location:locations:key

    String

    Camel 2.14.1: Lookup a property with the given key. The locations option is optional. See more at Using PropertyPlaceholder.

    properties:key:defaultStringCamel 2.14.1: Lookup a property with the given key. If the key does not exists or has no value, then an optional default value can be specified.

    routeId

    String

    Camel 2.11: Returns the id of the current route the Exchange is being routed.

    threadName

    String

    Camel 2.3: Ret urns the name of the current thread. Can be used for logging purpose.

    ref:xxx

    Object

    Camel 2.6: To lookup a bean from the Registry with the given id.

    type:name.field

    Object

    Camel 2.11: To refer to a type or field by its FQN name. To refer to a field you can append .FIELD_NAME. For example you can refer to the constant field from Exchange as: org.apache.camel.Exchange.FILE_NAME

    .

    null

     

    Camel 2.12.3: represents a null

    OGNL expression support

    Available as of Camel 2.3

    Icon

    Camel's OGNL support is for invoking methods only. You cannot access fields.
    From Camel 2.11.1 onwards we added special support for accessing the length field of Java arrays.

    @@ -18920,11 +18920,11 @@ template.send("direct:alias-verify&

    The cxf: component provides integration with Apache CXF for connecting to JAX-WS services hosted in CXF.

    +/*]]>*/

    • CXF Component
      • URI format
      • Options
        • The descriptions of the dataformats Modified: websites/production/camel/content/book-languages-appendix.html ============================================================================== --- websites/production/camel/content/book-languages-appendix.html (original) +++ websites/production/camel/content/book-languages-appendix.html Thu Feb 5 11:20:11 2015 @@ -1066,7 +1066,7 @@ result = body * 2 + 1

          The Simple language have been improved from Camel 2.9 onwards to use a better syntax parser, which can do index precise error messages, so you know exactly what is wrong and where the problem is. For example if you have made a typo in one of the operators, then previously the parser would not be able to detect this, and cause the evaluation to be true. There is a few changes in the syntax which are no longer backwards compatible. When using Simple language as a Predicate then the literal text must be enclosed in either single or double quotes. For example: "${body} == 'Camel'". Notice how we have single quotes around the literal. The old style of using "body" and "header.foo" to refer to the message body and header is @deprecated, and its encouraged to always use ${ } tokens for the built-in functions.
          The range operator now requires the range to be in single quote as well as shown: "${header.zip} between '30000..39999'".

    -

    To get the body of the in message: "body", or "in.body" or "${body}".

    A complex expression must use ${ } placeholders, such as: "Hello ${in.header.name} how are you?".

    You can have multiple functions in the same expression: "Hello ${in.header.name} this is ${in.header.me} speaking".
    However you can not nest functions in Camel 2.8.x or older (i.e. having another ${ } placeholder in an existing, is not allowed).
    From Camel 2.9 onwards you can nest functions.

    Variables

    Variable

    Type

    Description

    camelId

    String

    Camel 2.10: the CamelContext name

    camelContext.OGNL

    Object

    Camel 2.11: the CamelContext invoked using a Camel OGNL expression.

    exchangeId

    String

    Camel 2.3: the exchange id

    id

    String

    the input message id

    body

    Object

    the input body

    in.body

    Object

    the input body

    body.OGNL

    Object

    Camel 2.3: the input body invoked using a Camel OGNL expression.

    in.body.OGNL

    Object

    Camel 2.3: the input body invoked using a Camel OGNL expression.

    bodyAs(type)

    Type

    Camel 2.3: Converts the body to the given type determined by its classname. The converted body can be null.

    mandatoryBodyAs(type)

    Type

    Camel 2.5: Converts the body to the given type determined by its classname, and expects the body to be not null.

    out.body

    Object

    the output body

    header.foo

    Object

    refer to the input foo header

    header[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    headers.foo

    Object

    refer to the input foo header

    headers[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    in.header.foo

    Object

    refer to the input foo header

    in.header[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    in.headers.foo

    Object

    refer to the input foo header

    in.headers[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    header.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lookup on the map with bar as key

    in.header.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lookup on the map with bar as key

    in.headers.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and pe rform lookup on the map with bar as key

    header.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    in.header.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    in.headers.foo.OGNL

    Object

    Camel 2.3: refer to the in put foo header and invoke its value using a Camel OGNL expression.

    out.header.foo

    Object

    refer to the out header foo

    out.header[foo]

    Object

    Camel 2.9.2: refer to the out header foo

    out.headers.foo

    Object

    refer to the out header foo

    out.headers[foo]

    Object

    Camel 2.9.2: refer to the out header foo

    headerAs(key,type)

    Type

    Camel 2.5: Converts the header to the given type determined by its classname

    headers

    Map

    Camel 2.9: refer to the input headers

    in.headers

    Map

    Camel 2.9: refer to the input headers

    < p>property.foo

    Object

    refer to the foo property on the exchange

    property[foo]

    Object

    Camel 2.9.2: refer to the foo property on the exchange

    property.foo.OGNL

    Object

    Camel 2.8: refer to the foo property on the exchange and invoke its value using a Camel OGNL expression.

    sys.foo

    String

    refer to the system property

    sysenv.foo

    String

    Camel 2.3: refer to the system environment

    exception

    Object

    Camel 2.4: Refer to the exception object on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    exception.OGNL

    Object

    < strong>Camel 2.4: Refer to the exchange exception invoked using a Camel OGNL expression object

    exception.message

    String

    Refer to the exception.message on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    exception.stacktrace

    String

    Camel 2.6. Refer to the exception.stracktrace on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    < /td>

    date:command:pattern

    String

    Date formatting using the java.text.SimpleDataFormat 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

    Invoking a bean expression using the Bean language. Specifying a method name you must use dot as separator. We also support the ?method=methodname syntax tha t is used by the Bean component.

    properties:locations:key

    String

    Deprecated (use properties-location instead) Camel 2.3: Lookup a property with the given key. The locations option is optional. See more at Using PropertyPlaceholder.

    properties-location:locations:key

    String

    Camel 2.14.1: Lookup a property with the given key. The locations option is optional. See more at Using PropertyPlaceholder.

    properties:key:defaultStringCamel 2.14.1: Lookup a property with the given key. If the key does not exists or has no value, then an optional default value can be specified.

    routeId

    String

    Camel 2.11: Returns the id of the current route the Exchange is being routed.

    threadName

    String

    Camel 2.3: Returns the name of the current thread. Can be used for logging purpose.

    ref:xxx

    Object

    Camel 2.6: To lookup a bean from the Registry with the given id.

    type:name.field

    Object

    Camel 2.11: To refer to a type or field by its FQN name. To refer to a field you can append .FIELD_NAME. For example you can refer to the constant field from Exchange as: org.apache.camel.Exchange.FILE_NAME

    .

    null

     

    Camel 2.12.3: represents a null

    OGNL expression support

    Available as of Camel 2.3

    +

    To get the body of the in message: "body", or "in.body" or "${body}".

    A complex expression must use ${ } placeholders, such as: "Hello ${in.header.name} how are you?".

    You can have multiple functions in the same expression: "Hello ${in.header.name} this is ${in.header.me} speaking".
    However you can not nest functions in Camel 2.8.x or older (i.e. having another ${ } placeholder in an existing, is not allowed).
    From Camel 2.9 onwards you can nest functions.

    Variables

    Variable

    Type

    Description

    camelId

    String

    Camel 2.10: the CamelContext name

    camelContext.OGNL

    Object

    Camel 2.11: the CamelContext invoked using a Camel OGNL expression.

    exchangeId

    String

    Camel 2.3: the exchange id

    id

    String

    the input message id

    body

    Object

    the input body

    in.body

    Object

    the input body

    body.OGNL

    Object

    Camel 2.3: the input body invoked using a Camel OGNL expression.

    in.body.OGNL

    Object

    Camel 2.3: the input body invoked using a Camel OGNL expression.

    bodyAs(type)

    Type

    Camel 2.3: Converts the body to the given type determined by its classname. The converted body can be null.

    mandatoryBodyAs(type)

    Type

    Camel 2.5: Converts the body to the given type determined by its classname, and expects the body to be not null.

    out.body

    Object

    the output body

    header.foo

    Object

    refer to the input foo header

    header[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    headers.foo

    Object

    refer to the input foo header

    headers[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    in.header.foo

    Object

    refer to the input foo header

    in.header[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    in.headers.foo

    Object

    refer to the input foo header

    in.headers[foo]

    Object

    Camel 2.9.2: refer to the input foo header

    header.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lookup on the map with bar as key

    in.header.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and perform lookup on the map with bar as key

    in.headers.foo[bar]

    Object

    Camel 2.3: regard input foo header as a map and pe rform lookup on the map with bar as key

    header.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    in.header.foo.OGNL

    Object

    Camel 2.3: refer to the input foo header and invoke its value using a Camel OGNL expression.

    in.headers.foo.OGNL

    Object

    Camel 2.3: refer to the in put foo header and invoke its value using a Camel OGNL expression.

    out.header.foo

    Object

    refer to the out header foo

    out.header[foo]

    Object

    Camel 2.9.2: refer to the out header foo

    out.headers.foo

    Object

    refer to the out header foo

    out.headers[foo]

    Object

    Camel 2.9.2: refer to the out header foo

    headerAs(key,type)

    Type

    Camel 2.5: Converts the header to the given type determined by its classname

    headers

    Map

    Camel 2.9: refer to the input headers

    in.headers

    Map

    Camel 2.9: refer to the input headers

    < p>property.foo

    Object

    Deprecated: refer to the foo property on the exchange

    exchangeProperty.fooObjectCamel 2.15: refer to the foo property on the exchange

    property[foo]

    Object

    Deprecated: refer to the foo property on the exchange

    exchangeProperty[foo]ObjectC amel 2.15: refer to the foo property on the exchange

    property.foo.OGNL

    Object

    Deprecated: refer to the foo property on the exchange and invoke its value using a Camel OGNL expression.

    exchangeProperty.foo.OGNLObjectCamel 2.15: refer to the foo property on the exchange and invoke its value using a Camel OGNL expression.

    sys.foo

    String

    r efer to the system property

    sysenv.foo

    String

    Camel 2.3: refer to the system environment

    exception

    Object

    Camel 2.4: Refer to the exception object on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    exception.OGNL

    Object

    Camel 2.4: Refer to the exchange exception invoked using a Camel OGNL expression object

    exception.message

    String

    Refer to the exception.message on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    exception.stacktrace

    String

    Camel 2.6. Refer to the exception.stracktrace on the exchange, is null if no exception set on exchange. Will fallback and grab caught exceptions (Exchange.EXCEPTION_CAUGHT) if the Exchange has any.

    date:command:pattern

    String

    Date formatting using the java.text.SimpleDataFormat 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

    Invoking a bean expression using the Bean language. Specifying a method name you must use dot as separator. We also support the ?method=methodname syntax that is used by the Bean component.

    properties:locations:key

    String

    Deprecated (use properties-location instead) Camel 2.3: Lookup a property with the given key. The locations option is optional. See more at Using PropertyPlaceholder.

    properties-location:locations:key

    String

    Camel 2.14.1: Lookup a property with the given key. The locations option is optional. See more at Using PropertyPlaceholder.

    properties:key:defaultStringCamel 2.14.1: Lookup a property with the given key. If the key does not exists or has no value, then an optional default value can be specified.

    routeId

    String

    Camel 2.11: Returns the id of the current route the Exchange is being routed.

    threadName

    String

    Camel 2.3: Returns the name of the current thread. Can be used for logging purpose.

    ref:xxx

    Object

    Camel 2.6: To lookup a bean from the Registry with the given id.

    type:name.field

    Object

    Camel 2.11: To refer to a type or field by its FQN name. To refer to a field you can append .FIELD_NAME. For example you can refer to the constant field from Exchange as: org.apache.camel.Exchange.FILE_NAME

    .

    null

     

    Camel 2.12.3: represents a null

    OGNL expression support

    Available as of Camel 2.3

    Icon

    Camel's OGNL support is for invoking methods only. You cannot access fields.
    From Camel 2.11.1 onwards we added special support for accessing the length field of Java arrays.

    Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available.