-
-
Notifications
You must be signed in to change notification settings - Fork 15.8k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make transport.Bootstrap usable with no netty-resolver on classpath (#…
…13488) Motivation: Since some address families (e.g. unix sockets) do not need name resolver, It should be possible to exclude netty-resolver from classpath. Currently excluding name resolver leads to NoClassDefFoundError: AddressResolverGroup during Bootstrap instantiation. Modification: Add disableResolver() method to Bootstrap. Change BootstrapConfig.resolver() return null if Bootstrap.disableResolver() is called. Introduce ExternalAddressResolver class to hold AddressResolver related references to avoid NoClassDefFoundError if Bootstrap.disableResolver() called and no netty-resolver is on classpath. Result: Bootstrap is usable with no netty-resolver on classpath. --------- Co-authored-by: Chris Vest <mr.chrisvest@gmail.com>
- Loading branch information
1 parent
1ea8240
commit 9ce06cc
Showing
3 changed files
with
85 additions
and
11 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters