This chapter provides information and guidance for troubleshooting some of the most common issues that might be found in the Java 2D API when changing pipeline rendering and properties.
For a summary of Java 2D properties, see Appendix B.
By choosing a different pipeline, or manipulating the properties of a pipeline, you might be able to determine the cause of the problem, and often find a workaround.
In general you can troubleshoot Java 2D pipeline issues by determining the default pipeline used in your configuration. Then, either change the pipeline to another one, or modify the properties of the default pipeline.
If the problem disappears, you have found a workaround. If the problem persists, try changing another property or pipeline.
Java 2D uses a set of pipelines, which can be roughly defined as different ways of rendering the primitives. These pipelines are as follows:
Oracle Solaris and Linux: X11 Pipeline, which is the default for Oracle Solaris and Linux operating systems.
Windows OS - DirectDraw/GDI Pipeline is the default on Window.s
Windows OS - Direct3D Pipeline in Full-Screen Mode is an alternative on Windows.
OpenGL Pipeline in Oracle Solaris, Linux and Windows, which is an alternative on Oracle Solaris and Linux operating systems, as well as Windows.
