Paranamer error due to lack of debugging information in compiled class files

I am trying to run a spring package for an application deployed on websphere. When I run the package using eclipse everything works fine, but when I run the same batch in a deployed application on websphere, it gives an error

com.thoughtworks.paranamer.ParameterNamesNotFoundException: Parameter names not found for executeMethod at com.thoughtworks.paranamer.BytecodeReadingParanamer$TypeCollector.getParameterNamesForMethod(BytecodeReadingParanamer.java:209) 

I checked the source code of the Paranamer BytecodeReadingParanamer class and said

 if (!collector.isDebugInfoPresent()) { if (throwExceptionIfMissing) { throw new ParameterNamesNotFoundException("Parameter names not found for " + methodName); } else { return Paranamer.EMPTY_NAMES; } } 

I suppose this means that the java class was not compiled with debug information (-g flag?) In websphere, whereas in eclipse I have this information.

Please tell me how to fix this error on a web page? Do we have debugging information in compiled class java flags?

thanks

Aiden

+7
java parameters bytecode websphere
source share
1 answer

Thanks @minus, the problem was actually with the compiler, since there was an error on the compiler server. There was nothing wrong with the paranamer or the code itself. The compiler error should have been fixed.

+2
source share

All Articles