Thanks. I'd like to start a discussion on - What is the approach for specifying broker-specific properties? Different brokers might have different implementations and limitations. There are also times when there would be back-compat issues. I believe there is a lot of merit in exposing a way for custom broker-properties to be set/unset, which I'm thinking either goes through capabilities or properties on the connection.
-----Original Message----- From: Robbie Gemmell <[email protected]> Sent: Friday, December 13, 2019 6:17 AM To: [email protected] Subject: [EXTERNAL] Re: [Qpid JMS Client] What is the way to send custom properties / capabilities on AmqpConnection / AmqpSession / AmqpLink level? There is no mechanism for this currently, the JMS client internally sets properties+capabilities of its own or those required by the JMS mapping, but it is not possible for applications to set them. Robbie On Thu, 12 Dec 2019 at 22:01, Neeraj Makam <[email protected]> wrote: > > Hi, > > I am using Qpid-Jms-Client, version 0.46.0. > I want to be able to set custom properties on the AmqpConnection (sent via > the OPEN frame). > I control my AzureServiceBus broker as well. > > My use case is that I would like to create a wrapper around the > JmsConnectionFactory that takes care of authentication etc which is needed > for ServiceBus and let users directly use this wrapped > "ServiceBusJmsConnectionFactory" as a ConnectionFactory for all JMS > operations. > An alternative would be to adjust the user-agent details that QpidJms sends > to the broker. > Essentially, I want to a way to inform the ServiceBus broker that the usage > is happening from ServiceBusConnectionFactory as opposed to just > JmsConnectionFactory. > > Thanks, > Neeraj Makam --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
