And of course, I missed the fact that the last method in the class
contains a pathological use. To get the name of this class, we create a
parser ?
That's legacy code from pre-JAXP times. IIRC it is still used in the Batik bridge. The bridge needs an XML parser to parse references in the SVG to referencable items in other SVGs. The most ugly issue is mainly how to treat gradient="url('#foo')" stuff in embedded SVG code: #foo could in principle refer to an unresolvable node at the time it is needed because it is in another embedded code snippet further down the tree. FOP treats this as an error, embedded SVGs have to be self-contained. The spec is not helpful for guidance here.
That's not the only issue with the Batik bridge - the interface has been grown for some time.
Anybody out there willing to fix this?
