"trustin" wrote : A couple findings:
|
| 1) TransporterInvocation.readExternal(...) doesn't update the member variables but only the local final ones.
Yup, that's a bug. Fixing now...
"trustin" wrote : 2) TransporterInvocation.writeExternal(...) checks if the length values of parameterTypes and args are same, but I think this code should be moved to readExternal(...).
This is intentional. Only one length is written for both arrays, so it's checked on the write side. On the read side, they cannot differ since only one length is read.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190513#4190513
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190513
In a container, the core module will not be visible to the user's classloader; only the API will. So anything that we want to make available to the user must be in the API...
Alternately we could put it in core and expose an API for it in the standalone module classes (which would not be available in a container I guess; instead they would have to set up load-balancing in a configuration file).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190510#4190510
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4190510