You use the http: scheme to connect your client to a remote or external broker. You also have available other schemes like https:, tcp:, and ssl: to connect to a remote broker. Just depends what protocol you want to use.
The vm: scheme is used to start an intra-JVM or embedded broker. So if you use vm://bobert, you will launch and intra-JVM broker called "bobert". Joe Zanderfax wrote: > > So if my broker is running on server bob, I would change the value to > vm://bob:1234 or would it be http://bob:1234? > > J > > > > chago wrote: >> >> If you download ActiveMQ, the web demo module contains a few demos that >> use Jetty with an embedded broker talking to web pages using the amq.js >> script file. The embedded broker is configured in the web.xml file by >> specifying the vm://localhost value. If you want to use an external >> broker, you can just change this URL. >> >> Be sure to use Jetty 6.1.4. I had problems using Jetty 6.1.5. >> >> Please, point out any specific problems you run into. >> >> -- jim >> >> >> Zanderfax wrote: >>> >>> So my question is this: Is there any resource available that offers >>> step by step instructions on how to configure Jetty to talk with an >>> external broker and can use the amq.js mechanism for forwarding the >>> messages to a web page? >>> >> >> > > -- View this message in context: http://www.nabble.com/Looking-for-Help-ActiveMQ-and-Jetty-tf4379195s2354.html#a12533171 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
