Jndi support feature #93
Open
Conversation
This file contains hidden or 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
packaging of the project.
specified at runtime.
powered by AWS PrivateLink.
credentials as an AWS secret access key.
bug that did not close the connection.
|
Hi @adam-aws, @robin-aws, @kuba-aws and @haocheng-aws! Can any of you tell me why the contribution has not yet been reviewed? Thanks! |
|
is there any plan to merge this? Looking forward to this being available. Can you please prioritize. |
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.
Issue:
Small fit in test cases due to flaws found and mapped to ensure packaging of the project.
Description of changes:
Provides classes for accessing naming services that allows to be specified at runtime. It facilitates the migration of messages to the cloud of industry-application that supports the Java Naming API and Directory InterfaceTM (JNDI) standard. This enables you to move from any message broker that uses these standards to Amazon Simple Queue Service (SQS), simply by updating the endpoints of your applications.
Also enables the use of public IPs on the Internet or VPC endpoints that are powered by AWS PrivateLink.