Sorry Matt, I did not intend to suggest that it would work, just that it may
be a good candidate or direction for code change :-)
if it would work for you, please raise an enhancement jira so that the
requirement is captured. If you fancy making the changes your self on trunk,
attach a patch and I
Hi Gary, that was a great idea, and I hadn't tried it yet, but
ActiveMQ doesn't seem to like having anything else in the context
path. I get:
[WARN] TcpTransportFactory - path isn't a valid local location for
TcpTransport to use string: "/dynamicQueues/">java.lang.NumberFormatException: Fo
think you may have to modify the source to achieve what you want here.
Is the initial context used for destination lookup parametrised?
I wonder if a solution would be to have the provider url contain the context
in its path.
so something like: tcp://localhost:61616/dynamicQueues
such that the r
