After many hours, I have narrowed this bug to 
ProxyImplementationFactory... or rather the MethodGen object which it 
uses to construct this method based on the arbitratry method for a 
target proxy (createProxyMethod()).  The problem appears to be inside 
BCEL, though I am not sure and this shit is hard to read.

Basically the method signature byte code is getting messed up for long 
and double argument types, thus if you have an interface which has:

  void foo(long a, long b);

The current proxy compiler will not correctly generate the byte code for 
it.  I am assuming this is a problem inside of MethodGen or related BCEL 
classes, since I was able to take the exact BCEL code used to generate 
toString methods and it still failed.

I am guessing that the current BCEL impl does not reserve enough space 
for the parameter value or something like that... though I have not had 
time to read the spec to find out how all this fluff really works.

I am assuming that there is nothing wrong with the generated code inside 
based on my toString replacement test.

I will see if the BCEL folks can shed some light on this...

--jason


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to