[FEATURE REQ] Make it possible to inject desired subclass of ServiceBusJmsConnectionFactory into the configuration
Is your feature request related to a problem? Please describe. For our projects we have wrapper classes for several of the relevant JMS classes to provide additional functionality besides the standard stuff in servicebus. We therefore want to have our own ServiceBusConnectionFactory to generate our ServiceBusConnecion subclass.
Describe the solution you'd like We copied the existing ServiceBusJmsConnectionFactoryConfiguration and ServiceBusJmsConnectionFactoryFactory and with very small changes were able to get the desired outcome. The existing configuration code is pretty much already prepared for this improvement, all that is needed is a way to provide the desired class. Core to the solution is a very simple interface that can be implemented as a bean to state the desired class. PR will be provided.
Describe alternatives you've considered
Additional context The servicebus configuration is very similar to the one for Artemis and since we use both this functionality is requested there too. In case you come up with a different (read better) solution this should be coordinated with the Spring Boot Autoconfiguration/Artemis team.
Information Checklist Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report
- [x] Description Added
- [x] Expected solution specified
Ticket for Artemis https://github.com/spring-projects/spring-boot/issues/46365
@saragluna could you follow-up here
There is now a pull request available for review of the idea.
http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Virus-free.www.avg.com http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Wed, Jul 16, 2025 at 4:14 PM Alan Zimmer @.***> wrote:
alzimmermsft left a comment (Azure/azure-sdk-for-java#45942) https://github.com/Azure/azure-sdk-for-java/issues/45942#issuecomment-3078807592
@saragluna https://github.com/saragluna could you follow-up here
— Reply to this email directly, view it on GitHub https://github.com/Azure/azure-sdk-for-java/issues/45942#issuecomment-3078807592, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEMKQAG64MXKD6OHTVTM74L3IZM6FAVCNFSM6AAAAACBBRTODCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANZYHAYDONJZGI . You are receiving this because you authored the thread.Message ID: @.***>
We will close this issue as it has been open for a while. If you have any further questions or need assistance, please feel free to reopen it. Thank you!
So the idea is that you ignore an issue where there is even a pull request available for so long that you hope that the author will have forgotten it... A really great way to encourage community participation. But then again, M$ have happily ignored Bluetooth issues for 15+ years so I assume this is company standard practice. And no, I am not allowed to reopen the issue.
@thoroughsoft, sorry for wrongly closed this issue, I will review your PR.