rabbitmq / rabbitmq/rabbitmq-java-client
Make ConnectionFactory easier to use
@acogoluegnes is already working on this.
Since Apr 3, 2019.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 587
- Avg merge
- 7h 29m
- Merged PRs (30d)
- 41
Description
Related to #330.
Many settings have been added to ConnectionFactory over the years, making it somewhat harder to configure. It's for instance easy to omit an important option when setting TLS, because the different TLS-related options are scattered: ConnectionFactory#useSslProtocol, ConnectionFactory#setSslContextFactory, ConnectionFactory#enableHostnameVerification. Same thing for NIO (mitigated by NioParams).
A more "use-case oriented", less JavaBeans-like way could improve the situation, e.g.:
cf.nio().executor(myNioExecutor).socketChannelConfigurator(configurator) // NIO configuration
.connectionFactory() // going back to the connection factory (call may be avoided with syntax trick)
.tls().context(sslContext).hostnameVerification(true); // TLS configuration
Not longer useful configuration methods would be deprecated and scheduled for removal in 7.0.0.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.