. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 1.3.3. Handler Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 4.4.12. Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 4.4.13. Token Authentication . . . . . can also extend AbstractAnnotationConfigDispatcherServletInitializer and override specific methods (see the example under Context Hierarchy).  For programmatic use cases, a GenericWebApplicationContext

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 7.2. Hook methods for component lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 22.1. Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 25.15. Cut small classes and methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 7.2. Hook methods for component lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 22.1. Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 25.15. Cut small classes and methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 7.2. Hook methods for component lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 22.1. Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 25.15. Cut small classes and methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 7.2. Hook methods for component lifecycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 22.1. Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 25.15. Cut small classes and methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

sent between clients and servers. A message has a body which is a buffer containing convenient methods for reading and writing data into it. A message has a set of properties which are key-value pairs Artemis to use JAAS for security. Apache ActiveMQ Artemis can leverage JAAS to delegate user authentication and authorization to existing security infrastructure. The jms-auto-closeable example shows interest occur (consumers are created or closed, addresses are created or deleted, security authentication fails, etc.). JMS Context JMS Shared Consumer JMX Management Large Message Last-Value Queue

sent between clients and servers. A message has a body which is a buffer containing convenient methods for reading and writing data into it. A message has a set of properties which are key-value pairs Artemis to use JAAS for security. Apache ActiveMQ Artemis can leverage JAAS to delegate user authentication and authorization to existing security infrastructure. The jms-auto-closeable example shows interest occur (consumers are created or closed, addresses are created or deleted, security authentication fails, etc.). The message-counters example shows you how to use message counters to obtain

sent between clients and servers. A message has a body which is a buffer containing convenient methods for reading and writing data into it. A message has a set of properties which are key-value pairs Artemis to use JAAS for security. Apache ActiveMQ Artemis can leverage JAAS to delegate user authentication and authorization to existing security infrastructure. JMS Auto Closable The jms-auto-closeable interest occur (consumers are created or closed, addresses are created or deleted, security authentication fails, etc.). Message Counter The message-counters example shows you how to use message counters

sent between clients and servers. A message has a body which is a buffer containing convenient methods for reading and writing data into it. A message has a set of properties which are key-value pairs Artemis to use JAAS for security. Apache ActiveMQ Artemis can leverage JAAS to delegate user authentication and authorization to existing security infrastructure. JMS Auto Closable The jms-auto-closeable interest occur (consumers are created or closed, addresses are created or deleted, security authentication fails, etc.). Message Counter The message-counters example shows you how to use message counters

sent between clients and servers. A message has a body which is a buffer containing convenient methods for reading and writing data into it. A message has a set of properties which are key-value pairs Artemis to use JAAS for security. Apache ActiveMQ Artemis can leverage JAAS to delegate user authentication and authorization to existing security infrastructure. JMS Auto Closable The jms-auto-closeable interest occur (consumers are created or closed, addresses are created or deleted, security authentication fails, etc.). Message Counter The message-counters example shows you how to use message counters