Classloading / Clarify Spec

[cruftex]

Umbrella ticket for classloading. Should serve for general discussion on the topic and link to the tickets of the detail changes.

In general, the spec says on page 17:

2.5. Execution Context
EntryProcessors, CacheEntryListeners, CacheLoaders, CacheWriters and
ExpiryPolicys (“customizations”) are instantiated and operate in the context of the CacheManager
URI and ClassLoader in which they were configured. This means at deployment time, instances of
these customizations must be available to and have access to application classes defined by the
ClassLoader for a Cache.

TODO:

• General clarification, e.g. "deployment time" probably means "runtime".
• Reflect issues we found and addressed in MR 1.1
• Check appearances of classloader in the API and make it consistent

[OndroMih]

Do we have any progress / agreement on this? I would be happy to know if I can help somehow.

[cruftex]

Hi Ondrej,

I have some reasonable ideas for the places I found so far, that need clarification and corrections. However, whether this fits for all scenarios (OSGi and EE) needs good testing. Furthermore, I am not sure whether I found all places that are affected by classloading issues so far.

How to help:

• Make a list of all API elements that are affected by classloading (and needs tests regarding this)
• Use cases and tests!
• Besides, reviewing my currently pending other PRs and give +1s would be good help, too. Those should be merged, before doing more or bigger changes, otherwise its lots of extra work for the re-basing.

I will set aside one week in November to do some more work on 1.1 and plan to produce a PR on every currently remaining issue.

BTW: Saw your other activity on the ML and will comment next, when I am back from vacation :)

[gregrluck]

Deployment and deployment time is a term used widely in the spec.