Expose the enable1Prefixes configuration on external (pooled) connection factories

In  messaging

Overview

When connecting to a remote broker the prefixes used for Artemis 1.5.x compatibility might not be required nor used. While this can be set for a pure client, in WildFly you can’t set it for the connection factory you are using. This feature aims to fix that by enabling to configure this at the connection factory level.

Issue Metadata

Issue

  • ENTESB-10484 Fuse is connecting to a remote broker 2.6.x where the topic is created by the broker itself without the prefix. They access this topic through a Wildfly connection factory which will append the compatibility prefix thus making the resolution of the topic name fail.

Dev Contacts

QE Contacts

jkasik

Testing By

[X] Engineering

[ ] QE

Affected Projects or Components

Other Interested Projects

Requirements

Hard Requirements

N/A

Nice-to-Have Requirements

N/A

Non-Requirements

N/A

Test Plan

Create a core queue on a remote broker without the prefixes and connect to it disabling the enable1Prefixes on the pooled-connection-factory to access it by its name. Create a core queue on a remote broker without the prefixes and try to connect to it without disabling the enable1Prefixes on the pooled-connection-factory to access it by its name.

Community Documentation

The feature will be documented in WildFly Admin Guide (in the Messaging Configuration section).