So, long term that XML config is indeed going away, but 0.22 only removes the broker XML configuration, and simply makes the virtualhosts XML configuration optional.
The VirtualHosts XML confguration can still be used in 0.22 and is indeed actually necessary to conduct most virtualhost level configuration outside creating queues and exchanges via the management interfaces. At this point, its likely to be quite a while before virtualhosts.xml actually goes away. Robbie On 26 March 2013 16:45, Fraser Adams <[email protected]> wrote: > As a slight aside, given that Jeremy's original question asked about > creating a fanout exchange with the context of "from the XML config" it's > probably worth mentioning the work that Robbie and yourself have been > leading on to migrate off/deprecate the XML config towards configuration > via the plugins (http/jmx etc.) and the JSON config. > > That won't help Jeremy initially if he's working on a current build, but > when he moves to 0.22 it'll be something to be aware of. > > Frase > > > On 26/03/13 16:22, Rob Godfrey wrote: > >> Hi Jeremy, >> >> when you say you got an NPE from the Java Broker, do you mean that there >> was an NPE in the log or System.out from the broker? If so can you post >> the stack trace here - we should definitely not do that no matter what >> address you are using. >> >> thanks, >> Rob >> >> On 26 March 2013 17:11, Jeremy Wagner <[email protected]> wrote: >> >> Hello Alex, >>> >>> Thank you for your help! I was able to get it configured correctly. I >>> created three queues to bind to the exchange. I then connected separate >>> listeners (using drain) to each queue. I attempted to send a message to >>> the >>> exchange using spout, but I got a NullPointerException from the Java >>> broker. I believe I am not specifying the address to the fanout exchange >>> correctly? Using the example that you gave me, what would be the correct >>> address for the test.fanout exchange for spout to be able to connect to >>> send a message? Thank you! >>> >>> Jeremy >>> >>> >>> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
