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 lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <25765830.post@talk.nabble.com>
Date: Tue, 6 Oct 2009 02:58:48 -0700 (PDT)
From: davidgeary <david.geary@aepona.com>
To: users@activemq.apache.org
Subject: Re: Enable discovery in embedded broker URL
In-Reply-To: <3a73c17c0910060246u69f5e7e6n5f6320f119c73d30@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <25752382.post@talk.nabble.com>
 <3a73c17c0910060246u69f5e7e6n5f6320f119c73d30@mail.gmail.com>


Thanks for the reply, the application context snippet in my original post
was a bit misleading as i was just using that to test out brokerURLs to try
to get it working, actually I'm trying to set it up from JNDI within another
product which allows me to set the initial context properties, currently I
have 

java.naming.provider.url =
vm://localhost?brokerConfig=xbean:file:/activemqconfig/activemq-broker.xml

And within the config file I have the broker set up something like you
describe, however for simplicity I was hoping to avoid the need for this
file and set it up with just a broker URL. 

ie

java.naming.provider.url =
vm:(broker:(tcp://localhost:61618,network:multicast://default)?persistent=false&brokerName=ec-amq) 

but including the discovery uri also

If its not possible I can just stick with what I have.


-- 
View this message in context: http://www.nabble.com/Enable-discovery-in-embedded-broker-URL-tp25752382p25765830.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.