Replies: 1 comment
-
Hi @AnshJai,
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I hope this message finds you well. I am reaching out to seek clarification on the AWS Advanced JDBC Wrapper, specifically regarding the following points:
Is the DB native connector dependency mandatory for the AWS Advanced JDBC Wrapper? Are there any alternative options available that we can consider?
Additionally, is there a plan to provide AWS RDS driver functionality with this wrapper to eliminate the need for a native driver?
In the event of security vulnerabilities or bugs in the MySQL connector JAR, what measures are in place? Will we be dependent on the MySQL community for fixes, or does AWS provide support for such issues?
We would like to highlight the specific JBoss configuration where we cannot utilize the AWS JDBC URL. We use
xa-datasource
, which requires a datasource class to be specified in the configuration, but the existing wrapper does not have this feature implemented. This limitation restricts our ability to leverage the benefits of the wrapper library effectively. Please provide guidance on how we can address this issue.We would like to inquire about the licensing terms associated with the MySQL native driver. Understanding the licensing implications is important for our compliance and operational considerations.
Regards,
Anshul
Beta Was this translation helpful? Give feedback.
All reactions