I forgot to mention; for the client you would use a discovery uri as follows.
discovery:(rendezvous://group1) Joe ttmdev wrote: > > Hi Suran, > > We're also using 5.0 and have not had any success with the "zeroconf:" > scheme. The broker hurls an exception when you try and use "zeroconf:" > > We are instead using the "rendezvous:" scheme for "Zero Configuration". > Here's an example snippet for the broker xml cfg file. > > <transportConnectors> > <transportConnector > name="default" > uri="tcp://localhost:61616" > discoveryUri="rendezvous://group1" > /> > </transportConnectors> > > <networkConnectors> > <networkConnector > name="default" > uri=" rendezvous://group1" > /> > </networkConnectors> > > Hope this helps, > Joe > > > > Suran Jayathilaka wrote: >> >> James Strachan wrote: >>> On 16/10/2007, ttmdev <[EMAIL PROTECTED]> wrote: >>> >>>> Cool. >>>> >>>> What threw me off is that the only reference in the source code to >>>> 'zeroconf' is a link to http://www.zeroconf.org within the >>>> RendezvousDiscoveryAgent, which appears to all be based on JmDNS? >>>> >>> >>> Yeah, we're using hte JmDNS library for ZeroConf. >>> >>> >> Many thanks to both James & Joe for your replies. >> >> I wonder if anyone could provide me with some tips on how to get >> zeroconf working for the 5.0 SNAPSHOTs. What changes will I need to make >> to the activemq.xml for activemq to start with zeroconf? Or should I try >> a programmatic approach? >> >> Again, I am grateful for any input. >> >> Suran >> >> >> >> > > -- View this message in context: http://www.nabble.com/zeroconf-trouble-tf4631872s2354.html#a13254940 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
