New configuration of EhCache

[pj892031]

Is your feature request related to a problem? Please describe.
The EhCache uses the file ehcache.xml to configure all caches. There is one known issue about the order of processing XML (it clashes with the discovery client). It was fixed by hotfix in #3266.

The aim of this issue is to remove the dependency that EhCache should be initiated before the Discovery client.

Describe the solution you'd like
There are multiple ways how to configure caches (see EhCache 3 documentation). It is not necessary to use XML files, especially since there is no requirement to modify configuration by configuration. Once the configuration is moved into Java code, there should not be any similar issues.

Describe alternatives you've considered

• count just on hotfix fix: Fix conflict of XML processing between EhCache and onboarding #3266
• replace EhCache with a different cache (Infinispan looks reasonable since the APIML uses it in other services, in theory cacheService - but maybe it is too heavy as replacement)
• replace format in enabler (XML > JSON to avoid parser)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[pj892031]

It is still valid

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[github-actions]

This issue has been automatically closed due to lack of activity. If you disagree, please comment on reason why and reopen the issue

[pj892031]

It was implemented for v3 as part of #3568 (see org.zowe.apiml.zaas.config.CacheConfig#cacheManager)