You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by "jungm (via GitHub)" <gi...@apache.org> on 2024/09/16 12:15:33 UTC
[PR] [TOMEE-4402] Remove JCache (JSR 107) API and its implementation (tomee)
jungm opened a new pull request, #1497:
URL: https://github.com/apache/tomee/pull/1497
See https://issues.apache.org/jira/browse/TOMEE-4402
JCache was afaik never part of the Jakarta EE specification and JCS is still using the javax.* namespace for CDI
So this has been broken since the first TomEE 9 releases but nobody complained
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [TOMEE-4402] Remove JCache (JSR 107) API and its implementation (tomee)
Posted by Markus Jung <ju...@apache.org>.
JCache in itself is isolated, yes. But many implementations (RI, Geronimo simple, JCS) also bring CDI integration code so you can actually use JCache annotations without interacting directly with the CacheManager.
As far as I'm aware there is no implementation that provides this CDI integration for modern (= jakarta) versions of CDI, not even something that is shaded.
This and the fact that the spec has been abandoned for more or less +5 years lead me to the conclusion that at least JCache + CDI is dead right now.
We could keep a plain JCache impl in TomEE, but IMO this is out of scope. TomEE wants to be a Jakarta EE (+ microprofile) implementation, JCache is neither of those right now.
My opinion isn't too strong on this matter, but these are the reasons why I removed this for now. If we find we want to keep it we can always revert.
Am 16. September 2024 23:17:19 MESZ schrieb Mark Struberg <st...@yahoo.de.INVALID>:
> There are quite a few specs in the javax namespace still. If they are isolated it's imo fine to include them. It's just another 'optional' library. And a very useful indeed!
>It's imo a matter of time when it will finally get moved over to jakarta.
>LieGrue,strub
>
> On Monday, 16 September 2024 at 14:15:36 CEST, jungm (via GitHub) <gi...@apache.org> wrote:
>
>
>jungm opened a new pull request, #1497:
>URL: https://github.com/apache/tomee/pull/1497
>
> See https://issues.apache.org/jira/browse/TOMEE-4402
> JCache was afaik never part of the Jakarta EE specification and JCS is still using the javax.* namespace for CDI
>
> So this has been broken since the first TomEE 9 releases but nobody complained
>
>
Re: [PR] [TOMEE-4402] Remove JCache (JSR 107) API and its implementation (tomee)
Posted by Richard Zowalla <ri...@zowalla.com>.
So do you think upgrading to JCS3 + shading it for Jakarta inside TomEE would be worth?
There are no bug reports for TomEE 9.x that it isn't working, so is anyone using it?
Gruß
Richard
Am 16. September 2024 23:17:19 MESZ schrieb Mark Struberg <st...@yahoo.de.INVALID>:
> There are quite a few specs in the javax namespace still. If they are isolated it's imo fine to include them. It's just another 'optional' library. And a very useful indeed!
>It's imo a matter of time when it will finally get moved over to jakarta.
>LieGrue,strub
>
> On Monday, 16 September 2024 at 14:15:36 CEST, jungm (via GitHub) <gi...@apache.org> wrote:
>
>
>jungm opened a new pull request, #1497:
>URL: https://github.com/apache/tomee/pull/1497
>
> See https://issues.apache.org/jira/browse/TOMEE-4402
> JCache was afaik never part of the Jakarta EE specification and JCS is still using the javax.* namespace for CDI
>
> So this has been broken since the first TomEE 9 releases but nobody complained
>
>
>--
>This is an automated message from the Apache Git Service.
>To respond to the message, please log on to GitHub and use the
>URL above to go to the specific comment.
>
>To unsubscribe, e-mail: dev-unsubscribe@tomee.apache.org
>
>For queries about this service, please contact Infrastructure at:
>users@infra.apache.org
>
>
Re: [PR] [TOMEE-4402] Remove JCache (JSR 107) API and its implementation (tomee)
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
There are quite a few specs in the javax namespace still. If they are isolated it's imo fine to include them. It's just another 'optional' library. And a very useful indeed!
It's imo a matter of time when it will finally get moved over to jakarta.
LieGrue,strub
On Monday, 16 September 2024 at 14:15:36 CEST, jungm (via GitHub) <gi...@apache.org> wrote:
jungm opened a new pull request, #1497:
URL: https://github.com/apache/tomee/pull/1497
See https://issues.apache.org/jira/browse/TOMEE-4402
JCache was afaik never part of the Jakarta EE specification and JCS is still using the javax.* namespace for CDI
So this has been broken since the first TomEE 9 releases but nobody complained
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [TOMEE-4402] Remove JCache (JSR 107) API and its implementation (tomee)
Posted by "jungm (via GitHub)" <gi...@apache.org>.
jungm merged PR #1497:
URL: https://github.com/apache/tomee/pull/1497
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tomee.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org