Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 652D71081A for ; Wed, 11 Sep 2013 16:19:52 +0000 (UTC) Received: (qmail 86964 invoked by uid 500); 11 Sep 2013 16:19:52 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 86893 invoked by uid 500); 11 Sep 2013 16:19:51 -0000 Mailing-List: contact issues-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 issues@camel.apache.org Received: (qmail 86885 invoked by uid 99); 11 Sep 2013 16:19:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Sep 2013 16:19:51 +0000 Date: Wed, 11 Sep 2013 16:19:51 +0000 (UTC) From: "Claus Ibsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-6733) Add documentation for new activemq-camel broker component in AMQ 5.9 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Claus Ibsen created CAMEL-6733: ---------------------------------- Summary: Add documentation for new activemq-camel broker component in AMQ 5.9 Key: CAMEL-6733 URL: https://issues.apache.org/jira/browse/CAMEL-6733 Project: Camel Issue Type: Task Components: documentation Reporter: Claus Ibsen Priority: Minor We have activemq-camel documentation at http://camel.apache.org/components At the bottom at the external component list. We should add a page about the new broker component in activemq-camel in AMQ 5.9 onwards. What we have so far is Robs blog post http://rajdavies.blogspot.se/2013/09/apache-camel-broker-component-for.html?spref=tw -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira