Ok. This means that usage of virtual hosts requires "management" at
host and/or network level, which was a bit of surprise for me ;).
I had envisioned that you, for example could specify the virtual host
in the connection URI, e.g. "tcp://brokerhost:61613?virtual_host=foo".
This way you would be able to access virtual hosts without requiring
any changes to the setup of the client hosts or the network (DNS). I
can see deployment scenarios where it could be "hard" to make such
changes possible, not from a technical perspective but from an
organizational/responsibility perspective.
Kind Regards
Lars
On 7 Feb, 13:37, Hiram Chirino <
hi...@hiramchirino.com> wrote:
> ---------- Forwarded message ----------
> From: Lars-Erik Helander <
leh...@gmail.com>
> Date: Mon, Feb 6, 2012 at 5:29 PM
> Subject: stompjms mailing list?
> To:
hi...@hiramchirino.com
>
> Hi Hiram,
>
> is there some mailing-list where usage of stompjms is discussed?
>
> I have a particular question: How do I connect to a specific virtual
> host on the Apollo broker from a JMS client?
>
> Kind Regards
>
> Lars
>
> --
>
> **
>
> *Hiram Chirino*
>
> *Software Fellow | FuseSource Corp.*
>
> *
chir...@fusesource.com |
fusesource.com*
>
> *skype: hiramchirino | twitter: @hiramchirino<
http://twitter.com/hiramchirino>
> *
>
> *blog: Hiram Chirino's Bit Mojo <
http://hiramchirino.com/blog/>*
>
> *
> *
>
> *
> *