activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: [Fixed] Programatically setting up a proxying broker
Date Fri, 04 Aug 2017 13:06:46 GMT
Ah, that makes sense. Those class names are a little confusing, and so is
the term "discovery" since it sounds like it should mean "runtime discovery
of dynamic information" but static discovery actually means "discovery from
a config file."

Since it sounds like you aren't planning to continue using your subclass,
then no problem.


On Aug 3, 2017 9:51 AM, "Mark Raynsford" <>

> On 2017-08-03T08:57:38 -0600
> Tim Bain <> wrote:
> >
> > My question was why you needed to subclass it in the first place.
> Ah, that was down to an error in thinking on my part when looking at
> the available network connectors. It went something like this: "Hm, need
> a NetworkConnector. Don't seem to need 'discovery', don't seem to need
> 'multicast', don't seem to need LDAP... Guess I'm supposed to provide
> my own subclass". I only realized my mistake when I tracked down which
> subclass is instantiated for the broker when running the binary
> distribution from the command line (DiscoveryNetworkConnector).
> --
> Mark Raynsford |

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message