[
https://issues.apache.org/jira/browse/MNEMONIC-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275510#comment-17275510
]
Wang, Gang commented on MNEMONIC-588:
-------------------------------------
As we discussed in the previous meeting, the extension mechanism that is used
to select concrete memory service by name in runtime can be removed from
project code for the sake of deprecation in higher version of OpenJDK. we
conclude that the user needs to specify the concrete memory service in code
that cannot be selected by name anymore. It actually don't sacrifice the
flexibility and still graceful to abstract memory service from caller
perspective.
> Re-design the memory service selection mechanism
> ------------------------------------------------
>
> Key: MNEMONIC-588
> URL: https://issues.apache.org/jira/browse/MNEMONIC-588
> Project: Mnemonic
> Issue Type: New Feature
> Components: Memory-Service
> Affects Versions: 0.14.0
> Reporter: Wang, Gang
> Priority: Major
> Fix For: 0.14.0
>
>
> The memory service loading relies on the old JDK extension mechanism that has
> got removed in JDK10 and later, please refer to the following linked page.
> [https://docs.oracle.com/javase/10/migrate/toc.htm#JSMIG-GUID-2C896CA8-927C-4381-A737-B1D81D964B7B]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
