Author: buildbot Date: Tue Feb 4 15:19:05 2014 New Revision: 896390 Log: Production update by buildbot for camel Modified: websites/production/camel/content/cache/main.pageCache websites/production/camel/content/camel-2130-release.html websites/production/camel/content/commercial-camel-offerings.html websites/production/camel/content/user-guide.html Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/camel-2130-release.html ============================================================================== --- websites/production/camel/content/camel-2130-release.html (original) +++ websites/production/camel/content/camel-2130-release.html Tue Feb 4 15:19:05 2014 @@ -87,7 +87,7 @@

Camel 2.13.0 release (currently in progress)

-

New and Noteworthy

Welcome to the 2.13.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

Fixed Issues

New Enterprise Integration Patterns

New Components

New Camel Maven Archetypes

New DSL

New Annotations

New Data Formats

New Languages

New Examples

New Tutorials

New Tooling

API changes

Known Issues

Dependency Upgrades

You can see any dependency changes using Camel Dependencies Version Differences web tool created by Tracy Snell from the Camel Team.

The below list is a best effort, and we may miss some updates, its better to use the Camel Dependencies Version Differences web tool which uses the released projects for comparison.

Internal changes

Changes that may affect end users

Important changes to consider when upgrading

Getting the Distrib utions

Binary Distributions

Description

Download Link

PGP Signature file of download

Windows Distribution

apache-camel-2.13.0.zip

apache-camel-2.13.0.zip.asc

Unix/Linux/Cygwin Dis tribution

apache-camel-2.13.0.tar.gz

apache-camel-2.13.0.tar.gz.asc

+

New and Noteworthy

Welcome to the 2.13.0 release which approx XXX issues resolved (new features, improvements and bug fixes such as...)

  • The MBean names registered by Camel JMX no longer include the hostname in the context part, eg before context=myHost/myCamelId and now after context=myCamelId. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel.
  • MBean naming in OSGi cleaned up to use simpler naming with symbolicName. Before we could have MBean names with duplicate bundle ids such as context=114-114-camel-6, which now is using the symbolic name instead, context=MyApplication.
  • When using multiple OSGi Blueprint <cm:property-placeholder>'s then Camel now favors using non-default placeholders, or the last property-placeholder defined in the Blueprint XML file. This allows for example to define default properties in one placeholder, and override these values in other placeholders.
  • FTP consumer allow to download a single named file without using the FTP LIST command. This allows to download a known file from a FTP server even when the user account does not have permission to do FTP LIST command.
  • FTP consumer allow to ignore file not found or insufficient file permission errors.
  • Data Format using marshal now leverages Stream caching out of th e box if enabled, which allows to marshal big streams and spool to disk, instead of being pure in-memory based.
  • Improved using Bean when the bean is looked up in the Registry, when using concurrent processing in the route.
  • Added cache option to beanRef and <bean> in the DSL. This avoids looking up the Bean from the Registry on each usage; this can safely be done for singleton beans.
  • Configuring Data Formats in XML attributes now supports reference lookup using the # syntax, eg <jaxb xmlStreamWriterWrapper="#myWriterWrapper" ..>
  • JDBC component now also support outputType to specify the expected output as either a List or single Object. As well allow to map to a bean using a BeanRowMapper to control the mapping of ROW names to bean properties.
  • Both Quartz as well as Quartz2 based ScheduledRoutePolicy has been improved to better support cluster setups (e.g. to not schedule jobs being already scheduled through another node inside a given cluster).
  • Reduced the work the Aggregate EIP does while holding a lock during aggregation, which can lead to improved performance in some use-cases.
  • JndiRegistry now implements all the find methods.
  • VM component now supports multipleConsumers=true across deployment units.
  • Added @PreConsumed to JPA consumer.
  • Added CamelFileName header support to the HDFS producer
  • Like as JpaConsumer now also JpaProducer of the JPA component supports the CamelEntityManager header.
  • Restlet consumer now supports returning custom headers as HTTP headers from the Camel Message.
  • Spring Java Config CamelConfiguration now automagically detects all RouteBuilder instances registered in the Spring context if CamelConfiguration#routes method is not overridden.
  • Added support for transferring custom headers with RabbitMQ component.
  • PGPDataFormat enables stream cache during unmarshaling.
  • FileIdempotentRepository now creates necessary parent direc tories together with the new repository file.
  • Properties component and property placeholder will now ignore non existing JVM and environment options as well if ignoreMissingLocation is set to true.
  • Improved Stream consumer to enrich the Message with headers about current index / completion flag.
  • Added @BeanInject to inject beans (obtained from the Registry) in your beans such as RouteBuilder classes.
  • Polished the Karaf commands to output tables sorted and auto calculated width, so the data is formatted nicely.
  • Introduced UnitOfWorkFactory to allow end users to use custom Un itOfWork implementations created by the factory.
  • Doing request/reply over JMS allows per individual message requestTimeout value by specifying the timeout value in the "CamelJmsRequestTimeout" header.
  • Quartz and Quartz2 components now enlist the quartz scheduler by default in JMX, unless configured to be disabled.
  • Twitter Component supports to set proxy.
  • Netty HTTP consumer now remembers the raw (not decoded) value of URI query in the "CamelHttpRawQuery" header.
  • Bean Validation can be now configured to use custom ValidationProviderResolver (CAMEL-7162)
  • TypeConverterRegistry exposes more information in JMX and allows to browse all the registered type converters.
  • Bean Validation is now shipped with the optional OSGi-friendly HibernateValidationProviderResolver (CAMEL-7168)

Fixed Issues

  • Fixed an ArrayIndexOutOfBoundsException with Message History when using SEDA
  • Fixed requestTimeout on Netty not triggering when we have received message.
  • Fixed Parameter Binding Annotations on boolean types to evaluate as Predicate instead of Expression
  • Fixed using File consumer with delete=true&readLock=fileLock not being able to delete the file on Windows.
  • Fixed Throttler to honor time slots after period expires (eg so it works consistently and as expected).
  • Fixed getting JMSXUserID property when consuming from ActiveMQ
  • Fixed interceptFrom to support property placeholders
  • Fixed a race condition in initializing SSLContext in Netty and Netty HTTP
  • Fixed using Recipient List, Routing Slip calling another route which is configured with NoErrorHandler, and an exception occurred in that route, would be propagated back as not-exhausted, allow the caller route to have its error handler react on the exception.
  • Fixed Quartz and exception was thrown when scheduling a job, would affect during shutdown, assuming the job was still in progress, and not shutdown the Quartz scheduler.
  • Fixed so you can configure Stomp endpoints using URIs
  • Fixed memory leak when using Language component with camel-script languages and having contentCache=false
  • Fixed Error Handler may log at WARN level "Cannot determine current route from Exchange" when using Splitter
  • Fixed camel-fop to work in Apache Karaf and ServiceMix
  • Fixed HDFS producer to use the configured UuidGenerator when generating split file names to avoid filename collisions
  • Fixed JpaProducer and JpaConsumer of the JPA component to not share/reuse the same EntityManager object which could cause problems if this would occur in the context of multiple/different threads.
  • Fixed HTTP4 to support multiple custom component names in use, each configured using different SSLContext.
  • Fixed Content Based Router using method call's as Predicates if threw an exceptio n, the Content Based Router will call next predicate before triggering Error Handler.
  • Fixed Netty HTTP producer with query parameters may use wrong parameters from a previous call.
  • Fixed Netty producer may cause NullPointerException in messageReceived in client handler, if a Channel was destroyed from the producer pool.
  • Fixed File and FTP consumer(s) when idempotent=true could not detect changed file(s) as a new file, but would regard the file as idempotent.
  • Fixed Stream consumer reading a file using groupLines would not read last group of message if there was not enough lines to hit the threshold.< /li>
  • Fixed deleting the done file if File or FTP consumer rollback and the moveFailed option is in use.
  • Fixed avro data format in OSGi not being able to load schema classes.
  • Fixed JMX when using custom beans in routes with @ManagedResource to expose JMX attributes/operations to not include Camel standard attributes/operations from its processors, which would be shown as unavailable in JMX consoles.
  • Fixed Quartz2 simple trigger repeat count default value not working causing the trigger to only fire once, instead of forever.
  • Fixed JMS with a JMSRepyTo header using a topic, was mistakenly used as a queue instead. 
  • Fixed CSV to not modify the p roperties of the strategy constants declared by org.apache.commons.csv.CSVStrategy which would cause side effects when multiple CsvDataFormat objects are concurrently in use.
  • Fixed camel-script may return result from previous evaluation instead of result from current exchange.

New Enterprise Integration Patterns

New Components

New Camel Maven Archetypes

  • camel-archetype-cxf-code-first-blueprint
  • camel-archetype-cxf-contract-first-blueprint

New DSL

New Annotations

New Data Formats

New Languages

New Examples

New Tutorials

New Tooling

API changes

  • The interface of http4 org.apache.camel.component.http4.HttpClientConfigurer's method configureHttpClient(HttpClient client) was changed to configureHttpCli ent(HttpClientBuilder clientBuilder)

Known Issues

  • Spring 4.x is not yet official supported.

Dependency Upgrades

You can see any dependency changes using Camel Dependencies Version Differences web tool created by Tracy Snell from the Camel Team.

The below list is a best effort, and we may miss some updates, its better to use the Camel Dependencies Version Differences web tool which uses the released projects for comparison.

  • AHC 1.7.20 to 1.7.21
  • APNS 0.1.6 to 0.2.3
  • Atomikos 3.8.0 to 3.9.2
  • AWS-SDK 1.5.1 to 1.6.3
  • Avro 1.7.3 to 1.7.5
  • BeanIO 2.0.6 to 2.0.7
  • Commons Httpclient 4. 2.5 to 4.3.1
  • Commons Httpcore 4.2.4 to 4.3.1
  • CXF 2.7.6 to 2.7.8
  • EHCache 2.7.2 to 2.8.0
  • Elasticsearch 0.20.6 to 0.90.5
  • FOP 1.0 to 1.1
  • Guave 14.0.1 to 15.0
  • Hazelcast 2.6 to 3.0.2
  • Hibernate Validator 5.0.1.Final to 5.0.3.Final
  • ICal4j 1.0.4 to 1.0.5.2
  • Jclouds 1.6.2-incubating to 1.7.0
  • Jettison 1.3.4 to 1.3.5
  • Jetty 7.6.9 to 8.1.12
  • Joda time 2.1 to 2.3
  • JRuby 1.7.4 to 1.7.5
  • Lucene 3.6.0 to 4.5.1
  • MongoDB Java Driver 2.11.2 to 2.11.3
  • MyBatis 3.2.2 to 3.2.4
  • OGNL 3.0.6 to 3.0.8
  • Quartz 2.2.0 to 2.2.1
  • RabbitMQ amqp Java Client 3.1.3 to 3.2.2.
  • Restlet 2.0.15 to 2.1.4
  • Saxon 9.5.0.2 to 9.5.1-2
  • Scala 2.10.2 to 2.10.3
  • Servlet API 2.5 to 3.0
  • SNMP4J 2.2.2 to 2.2.3
  • SolrJ 3.6.2 to 4.5.1
  • Spring Batch 2.2.1.RELEASE to 2.2.2.RELEASE
  • Spring Redis 1.0.4.RELEASE to 1.1.0.RELEASE
  • SSH D 0.8.0 to 0.9.0
  • TestNG 6.8.5 to 6.8.7
  • XStream 1.4.4 to 1.4.5

Internal changes

  • Add RouteAware API to inject Route for Service's in routes, for example the Consumer's of the routes.
  • IOHelper.gerCharsetName will now lookup key Exchange.CHARSET_NAME in header first and then fallback to property.
  • Camel Spring now longer automatic registers "spring-event://default" endpoint, which wasnt in use anyway.
  • BAM component now uses raw EntityManager JPA API instead of deprecated Spring JpaTemplate

Changes that may affect end users

  • Components depending on Servlet API has been upgrade from Servlet API 2.5 to 3.0
  • Jetty upgraded from 7.6.x t o 8.1.x
  • Hazelcast Component uses Object instead of String as the key.
  • Hazelcast Component atomic number producer was using incorrect name (CAMEL-6833). Name will be different with this release.
  • Hazelcast Component instance consumer was incorrectly writing headers to the "out" message as opposed to the "in" message. Headers are now written to the "in" message.
  • Hazelcast Component map/multimap consumer were sending header value "envict" when an item was evicted. This has been corrected and the value "evicted" is used now.
  • The enum value NON_BLOCKING has been removed in camel-apns as its no long er support in APNS itself.
  • DefaultTimeoutMap must call start to initialize the map before use.
  • @ExcludeRoutes test annotation now accepts only classes implementing RoutesBuilder interface.
  • The MBean names registered by Camel JMX no longer include the hostname in the context part, eg before context=myHost/myCamelId and now after context=myCamelId. Having the hostname in the MBean name does not bring much value, and in fact makes things more complicated as the mbean name changes depending on the host running Camel. There is an option includeHostName that can be configure as true to preserve the old behavior.
  • MBean naming in OSGi cleaned up to use simpler naming with symbolicName. Before we could have MBean names with duplicate bundle ids such as cont ext=114-114-camel-6, which now is using the symbolic name instead, context=MyApplication.
  • Added beforeAddRoutes and afterAddRoutes to org.apache.camel.component.servletlistener.CamelContextLifecycle in ServletListener Component
  • The Language component now no longer caches the compiled script as that could cause side-effects. You can set cacheScript=true to enable the previous behavior if your script is safe to do so.
  • The default value of urlDecodeHeaders option on Netty HTTP has been changed from true to false.

Important changes to consider when upgrading

  • Spring 3.1.x is no longer supported.
  • If using groupedExc hanges option on Aggregate EIP then the Exchanges is now stored on the message body as well. The old way of storing as a property is considered deprecated. See more details at Aggregate.

Getting the Distributions

Binary Distributions

Description

Download Link

PGP Signature file of download

Windows Distribution

apache-camel-2.13.0.zip

apache-camel-2.13.0.zip.asc

Unix/Linux/Cygwin Distribution

apache-camel-2.13.0.tar.gz

apache-camel-2.13.0.tar.gz.asc

The above URLs use redirection

Icon
Modified: websites/production/camel/content/commercial-camel-offerings.html ============================================================================== --- websites/production/camel/content/commercial-camel-offerings.html (original) +++ websites/production/camel/content/commercial-camel-offerings.html Tue Feb 4 15:19:05 2014 @@ -75,42 +75,7 @@ -

Commercial Camel Offerings

- -

Apache Camel is a widely used project. As such, several companies have built products and services around Camel. This page is dedicated to providing descriptions of those offerings and links to more information. Companies are definitely encouraged to update this page directly or send a mail to the Camel PMC with a description of your offerings and we can update the page. The products and services listed on this page are provided for information use only to our users. The Camel PMC does not endorse or recommend any of the products or services on this page. See below for information about what is appropriate to add to the page.

- -

Ameliant

-

Ameliant is a specialist consultancy based in London, UK that provides architectural consulting around the Apache integration stack (Camel, CXF, Servicemix, ActiveMQ) including the development of prototypes and troubleshooting of existing Camel applications.

- -

Code-House

-

Code-House is european service provider with own training programs covering Apache middleware projects (Camel, ServiceMix, ActiveMQ) on development and system operations level. We also offer dedicated management tool.

- -

Cyberlogic Consulting GmbH

-

Cyberlogic Consulting GmbH is a Swiss based consultancy. We pride ourselves in providing Swiss quality services including enterprise consulting, coding, systems integration, training and support for Apache Camel and the related Apache Open Source Software. We specialize in helping our clients to realize new projects and support the delivery of the project from end to end.

- -

Middleware360

-

Middleware360 Enterprise Integration consulting services

- -

OpenLogic

-

OpenLogic provide support

- -

Red Hat

-

Red Hat provides enterprise integration products that include enterprise developer and production support on Apache Camel, and other Apache open source integration projects - including training, packaged services and subscriptions, and tooling such as Fuse IDE, Fuse Management Console, and Fuse HQ.

- -

Savoir Technologies, Inc

-

Savoir Technologies, Inc provides enterprise consulting, training and support for Camel and a host of other Apache service containers. Savoir can provide best practice mentoring for developing with Camel, as well as architectural/design reviews, troubleshooting and SOA infrastructure implementations.

- -

Talend, Inc

-

Talend, Inc provides enterprise level services, training and support for Apache Camel and their Talend ESB product which is a repackaging of Apache Camel including a full, pre-configured OSGi runtime container.

- -

TouK

-

TouK provides enterprise integration consulting and system integration services as well as support for Apache Camel and Apache Servicemix. Their developers were involved in camel-activiti development.

- -

Policy for additions to this page

- -

Companies are free to add information about their products and services to this page (please keep entries in alphabetical order). The information must be factual and informational in nature and not be a marketing statement. Statements that promote your products and services over other offerings on the page will not be tolerated and will be removed. Such marketing statements can be added to your own pages on your own site, but not here.

- -

When in doubt, email the Camel dev list (see Mailing Lists) and ask. We'd be happy to help.

+

Commercial Camel Offerings

Apache Camel is a widely used project. As such, several companies have built products and services around Camel. This page is dedicated to providing descriptions of those offerings and links to more information. Companies are definitely encouraged to update this page directly or send a mail to the Camel PMC with a description of your offerings and we can update the page. The products and services listed on this page are provided for information use only to our users. The Camel PMC does not endorse or recommend any of the products or services on this page. See below for information about what is appropriate to add to the page.

Ameliant

Ameliant is a specialist consultancy based in London, UK that provides architectural consulting around the Apache integration stack (Camel, CXF, Servicemix, ActiveMQ) including the development of prototypes and troubleshooting of existing Camel applications; and code-intensive Camel training. Ameliant's principal consultant is co-author of the Apache Camel Developer's Cookbook.

Code-House

Code-House is european service provider with own training programs covering Apache middleware projects (Camel, ServiceMix, ActiveMQ) on development and system operations level. We also offer dedicated managem ent tool.

Cyberlogic Consulting GmbH

Cyberlogic Consulting GmbH is a Swiss based consultancy. We pride ourselves in providing Swiss quality services including enterprise consulting, coding, systems integration, training and support for Apache Camel and the related Apache Open Source Software. We specialize in helping our clients to realize new projects and support the delivery of the project from end to end.

Middleware360

Middleware360 Enterprise Integration consulting services

OpenLogic

OpenLogic provide support

Red Hat

Red Hat provides enterprise integration products that include enterprise developer and production support on Apache Camel, and other Apache open source integration projects - including training, packaged services and subscriptions, and tooling such as Fuse IDE, Fuse Management Console, and Fuse HQ.

Savoir Technologies, Inc

Savoir Technologies, Inc provides enterprise consulting, training and support for Camel and a host of other Apache service containers. Savoir can provide best practice mentoring for developing with Camel, as well as architectural/design reviews, troubleshooting and SOA infrastructure implementations.

Talend, Inc

Talend, Inc provides enterprise level services, training and support for Apache Camel and their Talend ESB product which is a repackaging of Apache Camel including a full, pre-configured OSGi runtime container.

TouK

TouK provides enterprise integration consulting and system integration services as well as support for Apache Camel and Apache Servicemix. Their developers were involved in camel-activiti development.

Policy for additions to this p age

Companies are free to add information about their products and services to this page (please keep entries in alphabetical order). The information must be factual and informational in nature and not be a marketing statement. Statements that promote your products and services over other offerings on the page will not be tolerated and will be removed. Such marketing statements can be added to your own pages on your own site, but not here.

When in doubt, email the Camel dev list (see Mailing Lists) and ask. We'd be happy to help.

Modified: websites/production/camel/content/user-guide.html ============================================================================== --- websites/production/camel/content/user-guide.html (original) +++ websites/production/camel/content/user-guide.html Tue Feb 4 15:19:05 2014 @@ -75,36 +75,14 @@ -

User Guide

+

User Guide

If you want to get more familiar with what Apache Camel has to offer, please try the following resources:

+/*]]>*/

-
- -

Wiki pages

- - - - -

PDF

- -

You can try the Manual if you want to get a PDF of this documentation.

- -

Other Resources.

- -

The Apache Camel: Integration Nirvana article by Jonathan Anstey, a great place to start your journey.

- -

The Camel in Action book.

- -

The Camel Components Poster - Free PDF, 36"x24" Print

- -

Try these online Articles and Tutorials.

+

Wiki pages

PDF

You can try the Manual if you want to get a PDF of this documentation.

Other Resources.

The Apache Camel: Integration Nirvana article by Jonathan Anstey, a great place to start your journey.

The Camel in Action< /a> book.

The Camel Components Poster - Free PDF, 36"x24" Print

Try these online Articles and Tutorials.