fix(java): Blacklist detection is also performed when the Class is registered. #1398
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a Class has been registered using
Fury#register
, it currently escapes blacklist detection, so correct it to always perform blacklist detection.FuryBuilder#suppressClassRegistrationWarnings
should remain the same asFuryBuilder#requireClassRegistration
. The warning log will only be suppressed whenrequireClassRegistration
is true, that is, it will only be output whenrequireClassRegistration
is not turned on and the Class is not registered.Integrate some code into
isSecure()
.