Hi Simon, you you give me some example code for your plan. Sounds good... Bernd
Perhaps a custom ActionListener could be created which looks in the ancestry of the component that triggers the action, and "activates" an o:separateConversationContext if it finds one. It should be possible to do this without needing to modify Orchestra itself, ie you wouldn't need to wait for an Orchestra patch in order to solve this issue (though obviously it would be good for Orchestra to do this by default).
