Messaging: Simplified configuration of connection to remote integrated messaging broker --------------------------------------------------------------------------------------- Key: WFLY-14412 URL: https://issues.redhat.com/browse/WFLY-14412 Project: WildFly Issue Type: Enhancement Reporter: Petr Hostalek Priority: Major Labels: activemq, artemis, messaging EAP 7.2 introduced a simplified configuration of remote connections to the remote Artemis-based messaging broker. Connectors, connection factories and queues/topics may be configured directly in the {{messaging-activemq}} subsystem so that the messaging server configuration isn't required at all: [https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...] [https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_ap...] However that makes use of the {{remote-connector}}. When connecting to the integrated messaging broker at the remote JBoss EAP instance, the most straightforward is to use the {{http-connector}}. This type of connector can be also configured directly in the {{messaging-activemq}} subsystem, however it requires the {{endpoint}} attribute to reference the {{http-acceptor}} which is intended for inbound connections and requires the messaging server configuration. But since we require only outbound connections to the remote instance there's no real use for the {{endpoint}} configuration here and there should be no need to have any messaging server configured. Could the {{endpoint}} attribute be made optional, at least right at the {{messaging-activemq}} level? Or could this be solved another way?