XML Graphics common components

The problem

The FOP codebase contains two Batik transcoders for PDF and PostScript which can be used independently of FOP and are distributed with Batik. The Batik team should be empowered to help maintain these transcoders, for example, after changes in Batik itself. Since Batik and FOP are both implementing an XML standard that creates graphical output there is some overlap between the two efforts. Last but not least, a Batik release didn't involve a FOP release until now which is something that must change.

The idea

The idea now is to create a common area where the parts of common interest between the two subprojects are jointly developed and maintained.


The plan

(Subject of discussion. Input welcome.)

Common repository

For the joint operations we need a common repository. Since we now have migrated both subprojects to Subversion we are in a good starting position for this.

Parts affected in FOP



[1] Some of these classes could be candidates to go into Jakarta Commons IO.

External dependencies:

Parts affected in Batik

The transcoders depend on several packages inside Batik. Obviously, we can't create a clean hierarchy without dependencies on Batik, at least for the PDF and PS transcoders. But we should do that for the parts where this is possible (PDF lib, fonts, images etc.).

Possible components coming from Batik:

Organization and naming

Naming the individual parts

Apache XML Graphics Commons

Possible layout in SVN

Updated Proposal 2a:

  +-- commons
        +-- branches
        +-- tags
        +-- trunk
             +-- codecs
             +-- fonts
             +-- image-adapters
             +-- java2d (Graphics2D implementations, Pattern extensions)
                  +-- pdf (PDF implementation)
                  +-- ps (PS implementation)
             +-- pdf
             +-- ps
             +-- rtf
             +-- utils
  +-- batik
        +-- branches
        +-- tags
        +-- trunk
  +-- fop
        +-- branches
        +-- tags
        +-- trunk
  +-- site


Notes on additional use cases for the separated components

work items