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 2270610469 for ; Tue, 6 Jan 2015 07:19:32 +0000 (UTC) Received: (qmail 43393 invoked by uid 500); 6 Jan 2015 07:19:33 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 43344 invoked by uid 500); 6 Jan 2015 07:19:33 -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 43335 invoked by uid 99); 6 Jan 2015 07:19:33 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Jan 2015 07:19:33 +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 A7E21AC0958 for ; Tue, 6 Jan 2015 07:19:28 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r935232 - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache cometd.html Date: Tue, 06 Jan 2015 07:19:27 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150106071930.A7E21AC0958@hades.apache.org> Author: buildbot Date: Tue Jan 6 07:19:27 2015 New Revision: 935232 Log: Production update by buildbot for camel Modified: websites/production/camel/content/book-component-appendix.html websites/production/camel/content/book-in-one-page.html websites/production/camel/content/cache/main.pageCache websites/production/camel/content/cometd.html Modified: websites/production/camel/content/book-component-appendix.html ============================================================================== --- websites/production/camel/content/book-component-appendix.html (original) +++ websites/production/camel/content/book-component-appendix.html Tue Jan 6 07:19:27 2015 @@ -1024,74 +1024,23 @@ For example to use the MyFooBeanSee Also -

Cometd Component

- -

The cometd: component is a transport for working with the jetty implementation of the cometd/bayeux protocol.
-Using this component in combination with the dojo toolkit library it's possible to push Camel messages directly into the browser using an AJAX based mechanism.

- -

Maven users will need to add the following dependency to their pom.xml for this component:

-
- -
- -

URI format

- -
- -
- -

The channelName represents a topic that can be subscribed to by the Camel endpoints.

- -

Examples

-
+

The channelName represents a topic that can be subscribed to by the Camel endpoints.

Examples

cometd://localhost:8080/service/mychannel
 cometds://localhost:8443/service/mychannel
 
-
-

where cometds: represents an SSL configured endpoint.

- -

See this blog entry by David Greco who contributed this component to Apache Camel, for a full sample.

- -

Options

-
-

Name

Default Value

Description

resourceBase

 

The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar. Notice this option has been renamed to baseResource from Camel 2.7 onwards.

baseResource

 

Camel 2.7: The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar

timeout

240000

The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding.

interval

0

The client side poll timeout in milliseconds. How long a client will wait between reconnects

maxInterval

30000

The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time.

multiFrameInterval

1500

The client side poll timeout, if multiple connections are detected from the same browser.

jsonCommented

true

If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking.

logLevel

1

0=none, 1=info, 2=debug.

sslContextParameters

 

Camel 2.9: Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry.  This reference overrides any configured SSLContextParameters at the component lev el.  See Using the JSSE Configuration Utility.

crossOriginFilterOn

false

Camel 2.10: If true, the server will support for cross-domain filtering

allowedOrigins

*

Camel 2.10: The origins domain that support to cross, if the crosssOriginFilterOn is true

filterPath

 

Camel 2.10: The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true

disconnectLocalSession

true

Camel 2.10.5/2.11.1: (Producer only): Whether to disconnect local sessions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory.

- -
- -

You can append query options to the URI in the following format, ?option=value&option=value&...

- -

Here is some examples on How to pass the parameters

- -

For file (for webapp resources located in the Web Application directory --> cometd://localhost:8080?resourceBase=file./webapp
-For classpath (when by example the web resources are packaged inside the webapp folder --> cometd://localhost:8080?resourceBase=classpath:webapp

- -

Authentication

- -

Available as of Camel 2.8

- -

You can configure custom SecurityPolicy and Extension's to the CometdComponent which allows you to use authentication as documented here

- - -

Setting up SSL for Cometd Component

- -

Using the JSSE Configuration Utility

- -

As of Camel 2.9, the Cometd component supports SSL/TLS configuration through the Camel JSSE Configuration Utility.  This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels.  The following examples demonstrate how to use the utility with the Cometd component.

- -
Programmatic configuration of the component
- -
- -
- -
Spring DSL based configuration of endpoint
- -
- -
- - -

See Also

+

See Also

Context Component

@@ -1415,11 +1360,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-in-one-page.html ============================================================================== --- websites/production/camel/content/book-in-one-page.html (original) +++ websites/production/camel/content/book-in-one-page.html Tue Jan 6 07:19:27 2015 @@ -4126,11 +4126,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 @@ -6316,11 +6316,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 @@ -18838,74 +18838,23 @@ For example to use the MyFooBeanSee Also -

        Cometd Component

        - -

        The cometd: component is a transport for working with the jetty implementation of the cometd/bayeux protocol.
        -Using this component in combination with the dojo toolkit library it's possible to push Camel messages directly into the browser using an AJAX based mechanism.

        - -

        Maven users will need to add the following dependency to their pom.xml for this component:

        -
        - -
        - -

        URI format

        - -
        - -
        - -

        The channelName represents a topic that can be subscribed to by the Camel endpoints.

        - -

        Examples

        -
        +

        The channelName represents a topic that can be subscribed to by the Camel endpoints.

        Examples

        cometd://localhost:8080/service/mychannel
         cometds://localhost:8443/service/mychannel
         
        -
        -

        where cometds: represents an SSL configured endpoint.

        - -

        See this blog entry by David Greco who contributed this component to Apache Camel, for a full sample.

        - -

        Options

        -
        -

        Name

        Default Value

        Description

        resourceBase

         

        The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar. Notice this option has been renamed to baseResource from Camel 2.7 onwards.

        baseResource

         

        Camel 2.7: The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar

        timeout

        240000

        The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding.

        interval

        0

        The client side poll timeout in milliseconds. How long a client will wait between reconnects

        maxInterval

        30000

        The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time.

        multiFrameInterval

        1500

        The client side poll timeout, if multiple connections are detected from the same browser.

        jsonCommented

        true

        If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking.

        logLevel

        1

        0=none, 1=info, 2=debug.

        sslContextParameters

         

        Camel 2.9: Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry.  This reference overrides any configured SSLContextParameters at the component lev el.  See Using the JSSE Configuration Utility.

        crossOriginFilterOn

        false

        Camel 2.10: If true, the server will support for cross-domain filtering

        allowedOrigins

        *

        Camel 2.10: The origins domain that support to cross, if the crosssOriginFilterOn is true

        filterPath

         

        Camel 2.10: The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true

        disconnectLocalSession

        true

        Camel 2.10.5/2.11.1: (Producer only): Whether to disconnect local sessions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory.

        - -
        - -

        You can append query options to the URI in the following format, ?option=value&option=value&...

        - -

        Here is some examples on How to pass the parameters

        - -

        For file (for webapp resources located in the Web Application directory --> cometd://localhost:8080?resourceBase=file./webapp
        -For classpath (when by example the web resources are packaged inside the webapp folder --> cometd://localhost:8080?resourceBase=classpath:webapp

        - -

        Authentication

        - -

        Available as of Camel 2.8

        - -

        You can configure custom SecurityPolicy and Extension's to the CometdComponent which allows you to use authentication as documented here

        - - -

        Setting up SSL for Cometd Component

        - -

        Using the JSSE Configuration Utility

        - -

        As of Camel 2.9, the Cometd component supports SSL/TLS configuration through the Camel JSSE Configuration Utility.  This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels.  The following examples demonstrate how to use the utility with the Cometd component.

        - -
        Programmatic configuration of the component
        - -
        - -
        - -
        Spring DSL based configuration of endpoint
        - -
        - -
        - - -

        See Also

        +

    See Also

    Context Component

    @@ -19229,11 +19174,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/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/cometd.html ============================================================================== --- websites/production/camel/content/cometd.html (original) +++ websites/production/camel/content/cometd.html Tue Jan 6 07:19:27 2015 @@ -85,74 +85,23 @@ -

        Cometd Component

        - -

        The cometd: component is a transport for working with the jetty implementation of the cometd/bayeux protocol.
        -Using this component in combination with the dojo toolkit library it's possible to push Camel messages directly into the browser using an AJAX based mechanism.

        - -

        Maven users will need to add the following dependency to their pom.xml for this component:

        -
        - -
        - -

        URI format

        - -
        - -
        - -

        The channelName represents a topic that can be subscribed to by the Camel endpoints.

        - -

        Examples

        -
        +

        The channelName represents a topic that can be subscribed to by the Camel endpoints.

        Examples

        cometd://localhost:8080/service/mychannel
         cometds://localhost:8443/service/mychannel
         
        -
        -

        where cometds: represents an SSL configured endpoint.

        - -

        See this blog entry by David Greco who contributed this component to Apache Camel, for a full sample.

        - -

        Options

        -
        -

        Name

        Default Value

        Description

        resourceBase

         

        The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar. Notice this option has been renamed to baseResource from Camel 2.7 onwards.

        baseResource

         

        Camel 2.7: The root directory for the web resources or classpath. Use the protocol file: or classpath: depending if you want that the component loads the resource from file system or classpath. Classpath is required for OSGI deployment where the resources are packaged in the jar

        timeout

        240000

        The server side poll timeout in milliseconds. This is how long the server will hold a reconnect request before responding.

        interval

        0

        The client side poll timeout in milliseconds. How long a client will wait between reconnects

        maxInterval

        30000

        The max client side poll timeout in milliseconds. A client will be removed if a connection is not received in this time.

        multiFrameInterval

        1500

        The client side poll timeout, if multiple connections are detected from the same browser.

        jsonCommented

        true

        If true, the server will accept JSON wrapped in a comment and will generate JSON wrapped in a comment. This is a defence against Ajax Hijacking.

        logLevel

        1

        0=none, 1=info, 2=debug.

        sslContextParameters

         

        Camel 2.9: Reference to a org.apache.camel.util.jsse.SSLContextParameters in the Registry.  This reference overrides any configured SSLContextParameters at the component lev el.  See Using the JSSE Configuration Utility.

        crossOriginFilterOn

        false

        Camel 2.10: If true, the server will support for cross-domain filtering

        allowedOrigins

        *

        Camel 2.10: The origins domain that support to cross, if the crosssOriginFilterOn is true

        filterPath

         

        Camel 2.10: The filterPath will be used by the CrossOriginFilter, if the crosssOriginFilterOn is true

        disconnectLocalSession

        true

        Camel 2.10.5/2.11.1: (Producer only): Whether to disconnect local sessions after publishing a message to its channel. Disconnecting local session is needed as they are not swept by default by CometD, and therefore you can run out of memory.

        - -
        - -

        You can append query options to the URI in the following format, ?option=value&option=value&...

        - -

        Here is some examples on How to pass the parameters

        - -

        For file (for webapp resources located in the Web Application directory --> cometd://localhost:8080?resourceBase=file./webapp
        -For classpath (when by example the web resources are packaged inside the webapp folder --> cometd://localhost:8080?resourceBase=classpath:webapp

        - -

        Authentication

        - -

        Available as of Camel 2.8

        - -

        You can configure custom SecurityPolicy and Extension's to the CometdComponent which allows you to use authentication as documented here

        - - -

        Setting up SSL for Cometd Component

        - -

        Using the JSSE Configuration Utility

        - -

        As of Camel 2.9, the Cometd component supports SSL/TLS configuration through the Camel JSSE Configuration Utility.  This utility greatly decreases the amount of component specific code you need to write and is configurable at the endpoint and component levels.  The following examples demonstrate how to use the utility with the Cometd component.

        - -
        Programmatic configuration of the component
        - -
        - -
        - -
        Spring DSL based configuration of endpoint
        - -
        - -
        - - -

        See Also

        +

See Also