JD-GUI 1.0.0 in dynaTrace

Hi. I just double checked this with engineering. Seems like this is a bug on our side. We therefore recommend to stay on 0.3 until that will be fixed in a future dynatrace version. FYI - the internal bug number is JLT-127451 - in case you want to use this as a reference

Hi,

dynaTrace just calls an external decompiler with the executable and passing a temporary filename as parameter. Actually with jd-gui 1.x the command line does not accept a temporary file anymore. It must have exactly the same name as the encapsulated class. I will see if there is a workaround with using a batch file to call jd-gui performing a rename.

Please do consider that with 6.1 we updated the standard decompiler to a actual version of procyon, so the default output is much better than with 6.0 

regards
Harry 

Hi,

It seems feasible to call a batch file that performs a rename instead of calling jd-gui directly
So a call to 

D:\tools\jd-gui\callJDGUI.bat C:\dynatrace\client\cache\out\org.apache.derby.impl.jdbc.EmbedStatement5217584501740024027.class

will be transformed to

D:\tools\jd-gui\jd-gui.exe C:\dynatrace\client\cache\out\org.apache.derby.impl.jdbc.EmbedStatement.class

As standard rename command of windows is limited, you may have to use a external tool to accomplish that. But it may have some limitations, as numbers may be a valid part of the classname. In such cases jd-gui will not open the file.
regards
Harry 

Thanks Harald for the workaround!!

Hi Harald

Thanks for your help. Would you say that there's no need to use jd-gui with dynatrace 6.1 as the included decompiler is now equql or better than jd-gui?

Regards

Matthias

Hi,

The latest procyon version is equal to jd-gui

regards
Harry