Proposed workaround to the jakarta.mail.util.StreamProvider #702
Conversation
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
|
I think I have this case covered in #701 |
|
Hi, I made a specific test on the environment and code from #701 seems to work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently, when the instantiation of the StreamProvider Implementation fails using the Thread Context Class Loader, there's no fallback to the newInstance on the App Class Loader.
This is a proposed workaround, that allows to load the StreamProvider implementation class indicating the explicit class name (Declaration example under this line):
System.setProperty("jakarta.mail.util.StreamProvider","org.eclipse.angus.mail.util.MailStreamProvider");