If I understand you correctly, you have conversation A and conversation B. In conversation A you have some Seam component foo, and in conversation B you have some instantiated some component bar.
bar has an observer method that listens for fooEvent. You call a method on foo, which raises fooEvent. The observer method on bar will be called, but it won't be *the same instance* of bar that you have conversation B, but rather a new instance.
You can't observe an event raised in one conversation in another. If the observer was in the session scope or application scope this would work.
ok, so, how can I achieve some sort of "global event". Basically, I just need the bean in the "other conversation" to update from the DB so it can present fresh information if the user returns to this conversation.