Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 74.125.82.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1343247316670-4654365.post@n4.nabble.com>
References: <1343247316670-4654365.post@n4.nabble.com>
Date: Wed, 25 Jul 2012 21:54:07 +0100
Message-ID: 
 <CAH+vQmPTPzDi13Y8CKc1BO5yyx-b-1-Psmi8PeGvS7QPmeF7_Q@mail.gmail.com>
Subject: Re: composite uri
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I think the definition is a little loose, because folks use both
failover:// and failover:(..)

essentially the uri is composite if the scheme is followed by (..) so
the latter above is
composite. The urls are contained *within* the scheme specific part.

On 25 July 2012 21:15, mikmela <mikmela@yahoo.com> wrote:
> Can someone give the definition to the term "composite URI"?
> I thought, failover uri containting two uri's  as follows :
> /failover://(tcp://bla:61616,tcp://bla:61617)/
> is the composite URI, but
> URISupport.isCompositeURI(uri) returns false on it?
> Meanwile,
> CompositeData compositeData = URISupport.parseComposite(uri);
> does parse the same uri nicely, returning array with two URI objects?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/composite-uri-tp4654365.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.


-- 
http://fusesource.com
http://blog.garytully.com