We use XBean to perform the XML configuration. For details of the XML see the Xml Reference
ExamplesThe default ActiveMQ configuration: current default config. Error formatting macro: snippet: java.lang.IndexOutOfBoundsException: Index: 20, Size: 20
From a binary distribution there is an activemq script allowing you to run a Message Broker as a stand alone process from the command line easily providing the $ACTIVEMQ_HOME/bin directory is on your PATH. Configuring embedded brokersYou can also use the XML Configuration to configure embedded brokers. For example using the JNDI configuration mechanism you can do the following User Submitted ConfigurationsWe have a page which allows users to submit details of their configurations. BackgroundSince ActiveMQ has so many strategy pattern plugins for transports, wire formats, persistence and many other things, we wanted to leave the configuration format open so that you the developer can configure and extend ActiveMQ in any direction you wish. So we use the Spring XML configuration file format, which allows any beans / POJOs to be wired together and configured. However often Spring's XML can be kinda verbose at times, so we have implemented an ActiveMQ extension to the Spring XML which knows about the common, standard ActiveMQ things you're likely to do (e.g. tags like connector, wireFormat, serverTransport, persistence) - but at any time you can fall back to the normal Spring way of doing things (with tags like bean, property etc). To see documentation of the XML file we use or to get access to the XSD/DTD see the Xml Reference |
