Can not access cache in entry processor

Question

Why the cache where the entry object exists can not be accessed in entry processor?
The calculation in entry processor will not always be one grid object operation.
One object would be related to other objects.
If we could not do such thing in entry processor, we have to process calculation outside of the entry processor. However, caculation out of grid would not be a very efficient way for generating result.
Does anyone have good idea on this?

Answer 1

Hi, Robert,
I understood your meaning.
Invocable is an alternative solution for processing data. Use it outside of entry-processor, no dead lock would happen.
I paste piece of my code here. Following codes can not work properly. Just like you said, can not wait for result inside of entry-processor. My original purpose is that get "Nation" property from another data object. Now, I only can do it outside of entry-processor.
public class UpdateFxProcessor extends AbstractProcessor {
     public Object process(Entry entry) {
          HtWsMeasuresUsdFx hfx = (HtWsMeasuresUsdFx)entry.getValue();
     InvocationService service = (InvocationService)
CacheFactory.getConfigurableCacheFactory()
.ensureService("InvocationService");
     Map map = service.query(new NationInvocable(hfx.getWsNationCode()), null);
     String nation= (String)map.get(service.getCluster().getLocalMember());
          hfx.setNation(nation);     
// ... other logics for calculating hfx....
          return null;
My data grid environment will store more than 10 million HtWsMeasuresUsdFx objects. I hope that calculation on these objects could be executed in parallel. Maybe I misunderstood the function of entry-processor. If we use Invocable outside of entry-processor, it is hard to control its calculation in parallel, isn't it?
Best regards,
Copper