I am glad I finally managed to formulate my idea. "CptnKirk" wrote : On the other hand, somtimes you want global events, sometimes you want local events. Why not just say: "the scope for the events you want varies", from application-wide (the only choice ATM) to a conversation-wide.
"CptnKirk" wrote : Are conversations supposed to be able to communicate with each other via events? Bug or feature? Having scoped events does not mean full isolation, it means controlled isolation. If you want conversations to communicate via specific event, just bind the event high enough in scopes to be visible for both conversations. If you want the event to be private to the conversation, bind it in the conversation. The same idea works for bijection of values, why not generalize it to events as well? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947317#3947317 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947317 ------------------------------------------------------- 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
