Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Hi.

What approach could you suggest when implementing distributed master-worker application based on MasterWorker TIM and built over the Spring IoC?

Application uses WorkManager API. What if exact Work instance needed access to some local bean?

The only way I see is storing ApplicationContext somewhere in static property of some class and when Work object materialized on VM get access to ApplicationContext through this. But it is not very clear and would not be too readable as there could be a lot of different Work subclasses.

Thanks :)

unnutz wrote:

The only way I see is storing ApplicationContext somewhere in static property of some class and when Work object materialized on VM get access to ApplicationContext through this.

AFAIK, this is currently the only viable solution: some kind of static lookup.
You may also mark the injected field as transient, tell Terracotta not to share it among cluster nodes and then use Terracotta onLoad materialization for setting it in remote nodes, but that shouldn't differ that much from the first solution.
I was thinking of adding dependency injection facilities for materializing transient fields in distributed objects, but this is just a thought right now.

Cheers,

Sergio B.

sergiob wrote:

I was thinking of adding dependency injection facilities for materializing transient fields in distributed objects, but this is just a thought right now.

Mmm. Could you share your thoughts on this? How it can be implemented? APIs or whatever. I wish I could help and contribute into the code.

Thanks a lot.

Sincerely,
Artyom.

This is very old thread.Please respond if issue is still not resolved.
Thanks