Document about Jakarta namespace support
Closed this issue · 3 comments
javax.* is a thing of the past and should be considered for upgrading support for Jakarta
Hi @livk-cloud
Thanks for the input.
I'm curious what part of the datasource-proxy need to be the Jakarta namespace?
javax.sql.DataSource
is not affected because it is java SE api, not EE.
On the other hand, there are a few javax
usages in datasource-proxy in JNDI and query count via ServletRequestListener
.
Though, I don't think they are actively used by users. It doesn't mean I should just leave them as is, but it can be ignored for now.
If you need to use such functionality, you can easily write a similar one with jakarta package reference.
So, I'm curious what is your use case for the needs of the jakarta namespace.
thanks for your answer
The current design has javax, and if you consider that users will not actively use it, I think this part of the code should be removed, or migrated to a different library. I am currently learning datasource-proxy and may use this part of the feature
I'm re-purposing this ticket to a documentation task about Jakarta namespace support.