1.0 Introduction
2.0 Known problems and limitations
2.1
Running Java programs with non-Latin-1 characters in package or class names
2.2 Missing debug attributes
2.3 Setting breakpoints
2.4 Using Hot code
replace
2.5 Scrapbook
2.6 Debugging over slow connections
2.7 Updating of inspected values
2.8
Stepping over native methods that perform I/O
2.9 Searching for constant field references
2.10
Java compilation units outside of the build class path
2.11 VM
and process termination running on IBM 1.3 JVM on Linux
2.12 Actions to modify read-only files
2.13 Java code templates
2.14 Organize import and imports from default packages
2.15 Add Javadoc action for fields
2.16 Javadoc hover in the Java editor
2.17 HTML code >
displayed in new Java class instead of >
2.18 Cannot
run or debug class in a project with GB18030 characters in project name
2.19 Unable
to debug stack overflows
2.20 Evaluation
limitation
2.21 Breakpoints outside of the build class path
2.22 Quick fix and
imports from default packages
2.23 Cut,
copy, paste not working for linked resources in views showing Java elements
2.24
Java working sets not working correctly for elements from JRE system library
container
2.25
Cannot generate Javadoc for packages with GB18030 characters in the name
2.26 Linked editing does not work
correctly in overwrite mode
2.27 Catch block code
generation template must end with newline if last line is line comment
2.28 Problem opening class
file editor
This contains information on known problems and limitations with Java development tools.
rt.jar) are compiled without
complete debug attributes, and thus local variables and method arguments for
those classes are not visible in the debugger.
Hot code replace and stepping on JDK 1.4.0 VMs is unreliable.
When code is run in the scrapbook which directly or indirectly calls System.exit(int),
the evaluation cannot be completed, and will result in a stack trace for a com.sun.jdi.VMDisconnectedException
being displayed in the scrapbook editor.
Terminating a scrapbook page while it is performing an evaluation results in
a com.sun.jdi.VMDisconnectedException being displayed in the
scrapbook editor.
System.out
or System.err, the output may not appear immediately unless the
native performs a flush on the output buffer.
You cannot use ${CURSOR} inside of a comment in a Java code
template (Window > Preferences > Java > Templates).
Organize import does not handle imports from default packages. Note that importing from a default package is no longer supported in JDK 1.4.
The Add Javadoc action does not work for fields.
The Javadoc hover help shown when hovering over identifiers in the Java editor does not handle links inside of Javadoc comments properly.
When you create a new Java class, the generated comments reads:
To change the template for this generated file go to Windows >
Preferences > Java > Code Generation > Code and Comments.
The HTML code for greater than (>) sign is being used instead of the sign
itself. The comment should read:
To change the template for this generated file go to Windows > Preferences >
Java > Code Generation > Code and Comments.
Most class libraries do not properly support the creation of a system process
(via java.lang.Runtime.exec(...)) when the specified command line
contains GB18030 characters. This limitation means the debugger cannot launch
applications when the command line it generates contains GB18030 characters.
If a debug session suspends on a java.lang.StackOverflowError
exception (due to an exception breakpoint), the debugger may not be able to
retrieve any debug information from the target JVM. As well, the debugger may
not be able to reliably interact with the target JVM past this point.
The debugger uses threads in the target JVM to perform evaluations (both
explicit evaluations that the user requests, and implicit evaluations such as
toString() invocations in the Variables view). The Java
Debug Interface (JDI) requires that the thread in which an evaluation is
performed be suspended by a user event (that is, a breakpoint or step request).
Evaluations cannot be performed on threads suspended by the suspend action. As
well, when a breakpoint is configured to suspend the JVM rather than just the
individual thread, the threads which did not encounter the breakpoint are not in
a valid state to perform an evaluation. When an evaluation is attempted in a
thread that is not in a valid state to perform an evaluation, an error message
will appear to the effect of "Thread must be suspended by step or breakpoint to
perform method invocation".
Breakpoints can only be created on Java elements that are contained on the build class path of a project. The Java debugger automatically deletes breakpoints if their associated Java element is removed from the build path of a project. However, if the Java debug plug-in is not loaded when a build path is changed, such breakpoints will remain in the workspace, and can cause errors when the user attempts to go to the file associated with the breakpoint, from the Breakpoints view.
Quick fix does not handle imports from default packages. Note that importing from a default package is no longer supported in JDK 1.4.
The cut, copy, and paste actions do not work for linked files and folders appearing in views that show Java elements, including the Package Explorer. The workaround is to use these actions from the Navigator view instead.
Appling a working set consisting entirely of elements from the JRE System library container as a filter to the packages view might result in an empty Package Explorer.
Most class libraries do not properly support the creation of a system process
(via java.lang.Runtime.exec(...)) when the specified command line
contains GB18030 characters. Since Javadoc is created using the Javadoc
executable provided with the JDK, generating Javadoc fails if the package or
class name contains GB18030 characters.
Linked editing is used for renaming elements within a single compilation unit and for templates with multiple occurrences of the same template variable. Linked editing does not work correctly in overwrite mode.
If the last line of the catch block code generation template is a line comment then the line must be terminated with a newline. Otherwise the closing curly bracket ends up on the comment line, resulting in a compilation error.
If the "Use classpath containers" preference has been enabled on the Plug-in Development > Java Build Path Control preference page, you may not be able to open a class file editor for a class file contained in a JAR in the "Required plug-in entries" container. One way to work around the problem is to expand the class file in the Packages Explorer; this displays the class file's structure just as the editor would. If a source code zip is available for the JAR, another option is to attach source to the JAR file.
To attach source to a JAR in the "Required plug-in entries" container, follow these steps:
Return to the main readme file
(C) Copyright IBM Corporation 2000, 2003. All Rights Reserved.