Priming the OSB result cache

Hi,

We have some use-cases where it would be very beneficial to prime (pre-load) the OSB result cache when bringing the application up (for example via a separate webapp where the process starts with @postconstruct or contextInitalized, etc, fetching data from a DB and injecting this data into the Coherence OSB result cache (many ways to do this, but not important for the actual question).

There are examples out there for invalidating objects in the OSB result cache, probably using undocumented (?) functionality. I have started investigating how to "put" data in the cache in a way that the OSB can understand (according to what a business-service would expect when fetching from the cache). After playing around i bit, i can see that it is possible to fetch from the cache by using the "ResultCacheManager", then construct a "ResultCacheKey" by using a "Ref", a db operation and the actual value. This will return a "Result" object.