[ https://issues.jboss.org/browse/JASSIST-161?page=com.atlassian.jira.plugi... ] Shigeru Chiba commented on JASSIST-161: --------------------------------------- Can you make a simpler test case? It will help me so much. It's difficult to find a bug in the current test case because many class files (i.e. Process.java) are not given. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JASSIST-161?page=com.atlassian.jira.plugi... ] Joao Carvalho edited comment on JASSIST-161 at 3/20/12 5:22 AM: ---------------------------------------------------------------- EDIT: I have managed to track the code that's on the method being renamed, that is causing the exception (I've been trying different combinations until I found the one.) The method being processed has the code {{new FileRemoveLog(this, UserView.getCurrentUser(), file.getFilename(), file.getDisplayName() != null ? file.getDisplayName() : file.getFilename(), BundleUtil.getLocalizedNamedFroClass(file.getClass()));}} In which the FileRemoveLog constructors signature is {{public FileRemoveLog(WorkflowProcess process, User person, String... argumentsDescription)}} However, changing the code to the following will no longer raise the exception. {{ new FileRemoveLog(this, UserView.getCurrentUser(), file.getFilename(), /* * file.getDisplayName() != null ? file.getDisplayName() : * file.getFilename() */ BundleUtil.getLocalizedNamedFroClass(file.getClass()));}} was (Author: jpcarvalho): The actual test case isn't very relevant to this problem, we've tried with several versions of the injected method, like the original body, just printing something to System.out, empty body, all of them raise that exception. The injection code has been in production for quite a while, and simply renames the method, and wrapping a call to that method... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JASSIST-161?page=com.atlassian.jira.plugi... ] Shigeru Chiba commented on JASSIST-161: --------------------------------------- Thank you for your great help! I appreciate. For making a test case, usually, method names and class names do not matter. So you can use simple foo(), bar(), Foo, Bar, ... then I can run the test code without your whole application code. Thanks again, in fact, I cannot fix this kind of bug without your detailed bug report/test case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira