Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 22958 invoked from network); 20 Jan 2011 17:03:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Jan 2011 17:03:15 -0000 Received: (qmail 40748 invoked by uid 500); 20 Jan 2011 17:03:15 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 40570 invoked by uid 500); 20 Jan 2011 17:03:13 -0000 Mailing-List: contact dev-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 dev@camel.apache.org Received: (qmail 40562 invoked by uid 500); 20 Jan 2011 17:03:13 -0000 Delivered-To: apmail-activemq-camel-dev@activemq.apache.org Received: (qmail 40559 invoked by uid 99); 20 Jan 2011 17:03:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jan 2011 17:03:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jan 2011 17:03:12 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p0KH2pN8023681 for ; Thu, 20 Jan 2011 17:02:52 GMT Message-ID: <13123978.85101295542971754.JavaMail.jira@thor> Date: Thu, 20 Jan 2011 12:02:51 -0500 (EST) From: "Ben O'Day (JIRA)" To: camel-dev@activemq.apache.org Subject: [jira] Commented: (CAMEL-2989) provider an API to query available endpoints on a component MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-2989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984283#action_12984283 ] Ben O'Day commented on CAMEL-2989: ---------------------------------- Alright, thanks for the clarification. Sounds like this would require component specific implementations, but perhaps an interface could be added to the core to provide a framework for this. Overall, this starts to overlap with enhancing the management/monitoring of runtime routes/endpoints/exchanges, etc. I've used JMX for specific requirements for this in the past (AMQ queue mgmt, route start/stop/stats, etc)...but a more general framework for this would be nice. I'll think about this a bit... > provider an API to query available endpoints on a component > ----------------------------------------------------------- > > Key: CAMEL-2989 > URL: https://issues.apache.org/jira/browse/CAMEL-2989 > Project: Camel > Issue Type: New Feature > Components: camel-core > Affects Versions: 2.4.0 > Reporter: james strachan > Fix For: 3.0.0 > > > many components like file, activemq, nmr, jbi, database all are capable of browsing the available endpoints that a user could use from, say, a command line tool or from camel-web. > So we should add a browse API that lets you query a component for available endpoints. > Maybe allow things to be browsed in a tree kind of way - maybe with a text search type thing (for completion boxes etc) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.