. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 37.1. Pluggable Lock Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . communicates over the network using the "core" protocol. 5.1. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 37.1. Pluggable Lock Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . communicates over the network using the "core" protocol. 5.1. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 37.1. Pluggable Lock Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . communicates over the network using the "core" protocol. 5.1. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 37.1. Pluggable Lock Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . communicates over the network using the "core" protocol. 5.1. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing

communicates over the network using the "core" protocol. 5.1. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing activemq.artemis.spi.core.protocol.RemotingConnection that is passed in. If you perform some custom validation of the client ID you can reject the client ID by throwing a org.apache.activemq.artemis.core.protocol

downstream federated queues and addresses. Make security manager configurable via XML. Support pluggable SSL TrustManagerFactory. Add plugin support for federated queues/addresses. Support com.sun.jndi communicates over the network using the "core" protocol. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing

downstream federated queues and addresses. Make security manager configurable via XML. Support pluggable SSL TrustManagerFactory. Add plugin support for federated queues/addresses. Support com.sun.jndi communicates over the network using the "core" protocol. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing

downstream federated queues and addresses. Make security manager configurable via XML. Support pluggable SSL TrustManagerFactory. Add plugin support for federated queues/addresses. Support com.sun.jndi communicates over the network using the "core" protocol. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing

downstream federated queues and addresses. Make security manager configurable via XML. Support pluggable SSL TrustManagerFactory. Add plugin support for federated queues/addresses. Support com.sun.jndi communicates over the network using the "core" protocol. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing

downstream federated queues and addresses. Make security manager configurable via XML. Support pluggable SSL TrustManagerFactory. Add plugin support for federated queues/addresses. Support com.sun.jndi communicates over the network using the "core" protocol. Supported Protocols The broker has a pluggable protocol architecture. Protocol plugins come in the form of protocol modules. Each protocol module identifies the application. In some situations broker administrators may want to perform extra validation or even modify incoming client IDs to support specific use-cases. This is possible by implementing