Return-Path: Delivered-To: apmail-activemq-camel-dev-archive@locus.apache.org Received: (qmail 18688 invoked from network); 1 Dec 2008 19:53:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 Dec 2008 19:53:51 -0000 Received: (qmail 52048 invoked by uid 500); 1 Dec 2008 19:54:03 -0000 Delivered-To: apmail-activemq-camel-dev-archive@activemq.apache.org Received: (qmail 51974 invoked by uid 500); 1 Dec 2008 19:54:03 -0000 Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: camel-dev@activemq.apache.org Delivered-To: mailing list camel-dev@activemq.apache.org Received: (qmail 51963 invoked by uid 99); 1 Dec 2008 19:54:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Dec 2008 11:54:03 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com designates 74.125.92.146 as permitted sender) Received: from [74.125.92.146] (HELO qw-out-1920.google.com) (74.125.92.146) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Dec 2008 19:52:32 +0000 Received: by qw-out-1920.google.com with SMTP id 9so709465qwj.26 for ; Mon, 01 Dec 2008 11:53:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=4CQxiiuIR2wzVsebGC4vHCVJv/FkjcRLwD7jYjdDKZ8=; b=t5CJ/oLOhqQZJcrKiyx1g4pjmepCDTx34hF8DVubnTkN4rcnntvmDhW5w0UhkOyQeF odb+rRjblUg2Fid4IXMeiEX3Gj11NH8prBn1aP2w8eoJhAnRICkIgQHc+P55ZOzFsIvN HcwgaSc/3lOMWpeKXD2Tdmk+T/BtSKE0IN7Wc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=o8xj3dW0RrCaFTkm0qSx6esDCBgGkBCtcExbjPdCeQt2TxDIAGgj9b48Os6oKehosj OQfI2mBx6R6loWGP1R+2ejgUmzdRAVt7WdwY7sUdKWE7jWjEIF/b/Nzh4BBnEwvqj3bA ic6hWCPlyOqiwyoDCs3Bm9R19aNyrcgzh3YS4= Received: by 10.214.9.5 with SMTP id 5mr10295098qai.233.1228161199504; Mon, 01 Dec 2008 11:53:19 -0800 (PST) Received: by 10.214.9.14 with HTTP; Mon, 1 Dec 2008 11:53:19 -0800 (PST) Message-ID: <5380c69c0812011153j34eb02c6nea37e420eb2de2a@mail.gmail.com> Date: Mon, 1 Dec 2008 20:53:19 +0100 From: "Claus Ibsen" To: camel-dev@activemq.apache.org Subject: Re: [2.0] simplifying annotations, DSL and XML to remove uri + ref? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org Hi James Maybe you dot get to much sleep at nights now ;) But I had to do a 2nd pass to read and understand your mail. Are you suggesting that we can merge the uri and ref @annotation attribute and this imply a single attribute that supports both? If so what should be the name of this attribute? I currently like that the uri / ref style as you are in no doubt what they do. But is there a tremendous difference in the code base to support both? I was wondering if we should do a stratety as - look in registry first, if match use it - if no match create an endpoint with the provided text eg: @EndpointInject(uri="foo") @EndpointInject(uri="jms:queue:bar") So if there is a foo in the registry it is used. As there is no bean in the regsitry with jms:queue:bar an endpoint will be created Yeah you can do: uri="ref:foo" but I doubt that many end users know this. But I haven't played so much with the annotations as you have, so I am sure you are on to something. /Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/ On Mon, Dec 1, 2008 at 5:50 PM, James Strachan wrote: > Many places in Camel take a uri or a ref. e.g. > > @EndpointInject(uri="foo") or @EndpointInject(ref="bar") > > I wonder if given we've a ref component so we can use a uri of > "ref:bar" for a reference; should we do away with the difference > between them in the annotations/DSL/APIs for 2.0? > > -- > James > ------- > http://macstrac.blogspot.com/ > > Open Source Integration > http://fusesource.com/ >