I guess the theory in Seam is that the event "payload" is held in the contexts. ie. if you look at how all other events (jsf events, jbpm events, etc) work, the idea is that you don't couple your event listener to the event it is listening to via some Event object, instead, the event listener has no parameters and simply pulls state from the contexts. In a sense, an Event object is a hack for carrying information about contextual state in architectures which do not have well-defined contexts.
However, I am not religious about this, and if people want it, I can probably make the signature of raiseEvent() be raiseEvent(String, Object...), and then try to match the varargs off against the parameters of the listener method. But notice how this really does couple the event producer more tightly to the consumer. (I would have some problems with polymorphic type matching of parameters to overloaded listener methods, but those problems are probably not insurmountable.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955084#3955084 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955084 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
