"CptnKirk" wrote : He wants a way for events to be restricted to the context of the emitter. So he can have local conversation scoped events without worry that this event will bleed into observers in other conversations.
Sounds to me like he is asking for the exact opposite. "CptnKirk" wrote : Apparently eventhough the @Observer method is defined by a scoped component, it is still observing events globally. No, event processing takes place in the same conversation that produced the event. "CptnKirk" wrote : On the other hand, somtimes you want global events, sometimes you want local events. I'm guessing there's a request in here somewhere for the ability to specify some sort of event filter. We can do "local", we can't do "global". "CptnKirk" wrote : Are conversations supposed to be able to communicate with each other via events? Bug or feature? Conversations are able to communicate with each other via session-scoped components, or via components held in a containing conversation. They are not able to communicate via events. It would not be impossible to implement an event that is distributed to all conversations in a particular session, but it would be impossible to implement eg. all conversations in all sessions. not convinced that I like the idea. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947402#3947402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947402 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
