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_application_platform/7.2/html/7.2.0_release_notes/new_features_and_enhancements#messaging
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.3/html/configuring_messaging/resource_adapters#using_jboss_amq_for_remote_jms_communication

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?