3.0 comes with a very abstracted invocation structure. Those who are coming to the SF training will learn all about the new client architecture and its power essentially EJB is totally deconstructed we work solely at the MBean level.
It strikes me that benches out there are doing 2 things 1- measure how much the proxy sends 2- measure the difference between reflection and straight invocation the 2nd point we dont care, really, it is a property of the "implementation" of the VM and reflection while a weakness in 1.3.1. is also the strength of JBoss' implementation in the modularity and compilation less and bla bla bla. The first point we can do something about, right now we are going to send a map over the wire. I am thinking that in we could cheat and have a bare JRMPInvoker that just takes the invocation and send the data (id, method, params, tx, security) in a simple object without the map structure. This would of course break all custom interceptor stuff (where you actually pass data back and forth) but would enable a "cheat mode" for all EJBs. It would be a worthy optimization of the 3.1 series. marcf xxxxxxxxxxxxxxxxx Marc Fleury, Ph.D President JBoss Group, LLC xxxxxxxxxxxxxxxxx _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
