You can also use explicit code - e.g.
BrokerService broker = new BrokerService();
broker.setName("fred");
broker.setUseShutdownHook(false);
//Add a network connection
NetworkConnector connector =
answer.addNetworkConnector("static://"+"tcp://somehost:61616");
connector.setDuplex(true);
broker.addConnector("tcp://localhost:61616");
broker.start();
cheers,
Rob
http://open.iona.com/ -Enterprise Open Integration
http://rajdavies.blogspot.com/
On Dec 17, 2007, at 10:31 PM, ttmdev wrote:
For added flexibility, you can assign your embedded broker a broker
configuration file. For example,
vm://localbroker?brokerConfig=xbean:foo.xml
or
vm://localbroker?brokerConfig=xbean:file:C:/tmp/foo.xml
Joe
Hiram Chirino wrote:
it can easily be done if the embedded broker is embedded or if your
using the peer transport to implicitly create the embedded broker.
See:
http://activemq.apache.org/peer-transport-reference.html
On Dec 10, 2007 5:49 PM, xbranko <[EMAIL PROTECTED]> wrote:
Is it possible, and if so how, to configure forwarding bridge
between an
embedded broker and a remote broker?
--
View this message in context:
http://www.nabble.com/Forwarding-Bridge-between-embedded-broker-and-remote-broker-tp14263676s2354p14263676.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Regards,
Hiram
Blog: http://hiramchirino.com
Open Source SOA
http://open.iona.com
--
View this message in context:
http://www.nabble.com/Forwarding-Bridge-between-embedded-broker-and-remote-broker-tp14263676s2354p14375792.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
