Paul, I'll update the wiki tonight with your suggestions.
You asked earlier about:
"Can the following options also be used on a STOMP transport connector?
watchAdvisoryTopics, alwaysSessionAsync and dispatchAsync"
*Transport connectors* are a broker configuration, ie,
The options you asked abo
Hi Christian,
I am still a little confused given your previous answer. At first you state:
>No. those configure the TCP transport. They are not openwire or STOMP
>exclusive. They are also *not client or broker specific*. I can update the
>wiki, but they can more explicitly be set as '*transport.s
inline...
On Fri, May 10, 2013 at 6:44 PM, Paul Gale wrote:
> Hi Christian,
> *
> >What client are you using to connect with JMS?*
> Java JMS, .NET and Ruby based STOMP clients. I'm only involved with the
> Ruby clients. I have no idea how a JMS client is coded.
>
> Are all of these options res
Hi Christian,
*
>What client are you using to connect with JMS?*
Java JMS, .NET and Ruby based STOMP clients. I'm only involved with the
Ruby clients. I have no idea how a JMS client is coded.
Are all of these options reserved exclusively for non-STOMP clients?
http://activemq.apache.org/tcp-trans
s/JMS/the broker
On Fri, May 10, 2013 at 4:09 PM, Christian Posta
wrote:
> So you said transport connector... as in broker side... those options are
> for client-side connections and apply to the ActiveMQConnectionFactory.
> What client are you using to connect with JMS?
>
>
> On Fri, May 10, 20
So you said transport connector... as in broker side... those options are
for client-side connections and apply to the ActiveMQConnectionFactory.
What client are you using to connect with JMS?
On Fri, May 10, 2013 at 7:49 AM, Paul Gale wrote:
> Hi,
>
> Can the following options also be used on
Hi,
Can the following options also be used on a STOMP transport connector?
watchAdvisoryTopics, alwaysSessionAsync and dispatchAsync
Thanks,
Paul
