Thank you for the reply, James. The continuation is created in the InvocationHandler but the exception originates from within javaflow when it resumes the continuation. Please mind that this is not a basic question about proxies, as far as I understand it javaflow incorrectly restores the stack and tries to restore the proxy itself instead of the invocationhandler.
On Mon, Jun 11, 2012 at 1:05 PM, James Carman <[email protected]>wrote: > InvocationHandlers don't implement the interface. You'd have to have the > proxy instance itself. > > Sent from tablet device. Please excuse typos and brevity. > On Jun 11, 2012 4:55 AM, "George Georgovassilis" < > [email protected]> > wrote: > > > Hello list, > > > > I am trying to suspend a call where the stack goes through a dynamic > proxy. > > When resumed, I get a ClassCastException which tries to cast the > > InvocationHandler of the proxy to the interface it is proxying. Classes > are > > prepared with the ant-task, both bcel and asm modes fail.Can this be done > > and all and yes, then how? > > >
