throw new SecurityException("Not accessed
> over ssl");
> }
> } else {
> return super.addConsumer(context, info);
> }
> }
> --
> View this message in context
xception("Not accessed over
ssl");
}
} else {
return super.addConsumer(context, info);
}
}
--
View this message in context:
http://www.nabble.com/Secure-a-subset-of-destinations-tp14435506s2354p1459
On 03/01/2008, joe.stapleton <[EMAIL PROTECTED]> wrote:
> Thanks for the reply. Is it not possible to configure a set of destinations
> such that they can only be accessed from a particular transport where the
> broker actually exposes multiple transports?
Currently not; right now all transports a
Thanks for the reply. Is it not possible to configure a set of destinations
such that they can only be accessed from a particular transport where the
broker actually exposes multiple transports?
--
View this message in context:
http://www.nabble.com/Secure-a-subset-of-destinations
sport, one for open, but I'd like to avoid this if
> possible to avoid duplicating shared configuration. If we do need two
> brokers is it possible to define them both in the same xml config?
>
> Thanks in advance,
>
> Joe
>
--
View this message in context:
http://www.nabble.c
ance,
Joe
--
View this message in context:
http://www.nabble.com/Secure-a-subset-of-destinations-tp14435506s2354p14435506.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
