JDK-6566807 : Need pluggable interface to facilitate OpenJDK replacement of encumbered Ductus components
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2007-06-07
  • Updated: 2011-05-18
  • Resolved: 2011-05-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7 b14Fixed
Related Reports
Relates :  
JDK-6818072 - Load Ductus using Class.forName if exist instead of using the service loader
Description
Right now the 2D implementation depends directly on the encumbered code in
the Ductus library with no clean interface to isolate the implementation
for replacement.

We need to create an interface to the Ductus functionality and then modify
our internal rendering pipelines to go through it without any dependencies
on the Ductus interfaces.
Comments
EVALUATION The work is in progress. A pluggable abstract class was created with 3 methods to abstract away our dependencies on the Ductus code: sun.java2d.pipe.RenderingEngine.createStrokedShape() // for BasicStroke sun.java2d.pipe.RenderingEngine.getAATileGenerator() // for AA rendering sun.java2d.pipe.RenderingEngine.strokeTo() // mainly for non-AA wide paths
08-06-2007