Yes, https://fisheye6.atlassian.com/browse/activemq/trunk/activemq-optional/src/test/java/org/apache/activemq/bugs/AMQ2764Test.java?hb=true
tests network connectors over http scenario. Of course, you should test your use case. Regards -- Dejan Bosanac - http://twitter.com/dejanb ----------------- The experts in open source integration and messaging - http://fusesource.com ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Wed, Nov 9, 2011 at 5:19 PM, James Green <james.mk.gr...@gmail.com>wrote: > Just to be clear, we could ship software containing an embedded or > standalone broker that is told to connect to (for argument's sake) > https://broker1.mycompany.com:61616 and > https://broker2.mycompany.com:61616and it will form part of the broker > network allowing clients to connect > locally? > > James > > On 9 November 2011 15:32, Dejan Bosanac <de...@nighttale.net> wrote: > > > You can use http transport inside you network connector, no problem about > > that. > > > > Regards > > -- > > Dejan Bosanac - http://twitter.com/dejanb > > ----------------- > > The experts in open source integration and messaging - > > http://fusesource.com > > ActiveMQ in Action - http://www.manning.com/snyder/ > > Blog - http://www.nighttale.net > > > > > > On Wed, Nov 9, 2011 at 1:50 PM, James Green <james.mk.gr...@gmail.com > > >wrote: > > > > > Hi, > > > > > > The network connector is documented with tcp:// transport. Are there > > > others? > > > > > > For instance, imagine I want to install a broker that is behind a > > > customer's firewall, and connect it to a production network of brokers. > > > HTTP/S might be allowed by the customer for outbound connections but > > > nothing else. Is there an option here? > > > > > > Thanks, > > > > > > James > > > > > >
