The filename of the class(with source code included) should not end with .class on debugging scene

When we normally open a class with source code, its filename ends with .java. However, if we jump to a class with source code during debugging, the filename ends with .class. This results in the same class being opened twice (one ending with .java and the other with .class), which is very confusing. Could we standardize this behavior? If a class has source code, it should always be opened as a file ending with .java.

Meanwhile, a breakpoint has been set in the .java file (the Java source file of the class), but during debugging, the execution jumps to and breaks at the .class file instead. The breakpoint symbol is not displayed, yet it actually takes effect. This issue occurs because the same class has been opened with different file extensions.

Riproduci la navigazione del debugging con una classe Java che disponga del codice sorgente e confronta le voci .java e .class aperte. Segui il percorso del mapping del codice sorgente o della navigazione al breakpoint, quindi verifica che le classi associate al codice sorgente vengano aperte solo come file .java e che i simboli dei breakpoint compaiano in quel file.