Hi Folks, I'm not the java class file format familiar so asking in public. Would it be possible to update jboss-invocation generated byte code so the proxies it generates would be debugable? I'm facing the usability issue. I have an EJB3 impl class and when trying to debug its methods I'm getting the following error in IDE (see attachment).

Creating an empty table may change the message that you get, but it will not add any extra functionality. Using the line numbers from the superclass does not make sense, as there is no correlation between the proxies bytecode and the superclass bytecode. > From that message it sounds like you are trying to set a breakpoint into the proxy directly. Normally when debugging proxies I set a breakpoint in the calling code, then just keep hitting 'Step Into' until I get to the proxy handler.

Stuart On 03/05/2011, at 12:30 AM, David M. Lloyd wrote: > On 05/02/2011 09:22 AM, Richard Opalka wrote: >> Hi Folks, >> >> I'm not the java class file format familiar so asking in public. >> Would it be possible to update jboss-invocation generated byte code >> so the proxies it generates would be debugable? >> I'm facing the usability issue. I have an EJB3 impl class and when trying >> to debug its methods I'm getting the following error in IDE (see >> attachment). > Yeah I think we can use some of the line number information from the > superclass, maybe (it might not make sense). I can chat with Stuart > about it. > > At the least we can create an empty table, or maybe figure out what > reflection proxies do and do that. > -- > - DML > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev