The equals method on ActiveMQActivationSpec has a switched
null pointer verification for singleConnection and useJNDI fields.
Since both fields are initialized with a value by default it should
not be a problem but if one of these fields are set as null at some
point and then equals is called it throws a NPE.
destination.
* When creating a destination it should rely on the RA configuration if
none is provided instead of relying directly on the default
configuration.
Issue: https://issues.apache.org/jira/browse/ARTEMIS-2954
This commit does the following:
- Deprecates existing overloaded createQueue, createSharedQueue,
createTemporaryQueue, & updateQueue methods for ClientSession,
ServerSession, ActiveMQServer, & ActiveMQServerControl where
applicable.
- Deprecates QueueAttributes, QueueConfig, & CoreQueueConfiguration.
- Deprecates existing overloaded constructors for QueueImpl.
- Implements QueueConfiguration with JavaDoc to be the single,
centralized configuration object for both client-side and broker-side
queue creation including methods to convert to & from JSON for use in
the management API.
- Implements new createQueue, createSharedQueue & updateQueue methods
with JavaDoc for ClientSession, ServerSession, ActiveMQServer, &
ActiveMQServerControl as well as a new constructor for QueueImpl all
using the new QueueConfiguration object.
- Changes all internal broker code to use the new methods.
The parameter failoverOnInitialConnection wouldn't seem to be used and
makes no sense any more, because the connectors are retried in a loop.
So someone can just add the backup in the initial connection.
In some cases users who migrate from 1.x to 2.x may still want to keep
the legacy prefixes for their JMS destinations (i.e. "jms.queue.",
"jms.topic.", etc.). This commit adds a boolean on our ConnectionFactory
implementation so that it will use the old prefixes when invoking the
queue/topic creation methods on the Session implementation.
Artemis 1.x RA would do a core queue lookup if it could not find the
Destination in JNDI. We need to ensure that we can support the old
address model for backwards compatability.
We provide a feature to mask passwords in the configuration files.
However, passwords in the bootstrap.xml (when the console is
secured with HTTPS) cannot be masked. This enhancement has
been opened to allow passwords in the bootstrap.xml to be masked
using the built-in masking feature provided by the broker.
Also the LDAPLoginModule configuration (in login.config) has a
connection password attribute that also needs this mask support.
In addition the ENC() syntax is supported for password masking
to replace the old 'mask-password' flag.
Kerner, Dr. Patrick
Ryan Yeats
Domenico Francesco Bruscino
Clebert Suconic
Tiago Bueno
Asukwo-comfort
Andy Taylor
Emmanuel Hugonnet
Justin Bertram
brusdev
Patrick Zeller
Emmanuel Hugonnet
Jiri Danek
Romain Pelisse
Michael André Pearce
Ingo Weiss
Martyn Taylor
JiriOndrusek
Howard Gao