Employing GWT's RequestFactory within Activities?

I'm not sure this would work, but you could try to create another event bus.

I'm not sure this would work, but you could try to create another event bus : final EventBus customerActivityEventBus = new SimpleEventBus(); Initialize a new RequestFactory with this eventBus and use it in the CustomerActivity. CustomerActivityRequestFactory = GWT. Create(CustomerRequestFactory.

Class); customerActivityRequestFactory. Initialize(customeActivityEventBus); CustomerRequest context = customerActivityRequestFactory.customerRequest(); Your CustomerActivity will still listen to change events from the main eventBus but will not see the events it fired. In your other activities, listen to events either only from the customerActivityEventBus or from both, depending on what you want.

Of course, keep only one main eventBus to use for events that are not from a Request Factory (ie. ActivityManager, Place etc ..).

Not a bad idea. Problem would be that the other activity wouldn't get any EntityProxyChanges from CustomerActivity. I'm starting to think that these two activities need to be disintertwingled.

– David Jun 10 at 11:02 In such a case what I did is having 2 separate events thrown by the 2 activities. I know it's much more boiler plate code to be written, but those are serparate events indeed, even in your use case. If I had to refactor my code, now I'd have one event and a flag in it to test wether it is from one activity or the other.

– Christian Achilli Nov 30 at 13:50.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.