[XALANJ-2033] SerializationHandler interface should inlude DTDHandler

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7
• Component/s: Serialization
• Security Level: No security risk; visible to anyone (Ordinary problems in Xalan projects. Anybody can view the issue.)
• Xalan info: PatchAvailable
• Assignee: Brian Minchau
• Reporter: Brian Minchau
• Reviewer: Ilene Seelemann
• Created: 26/Dec/04 17:09
• Updated: 01/Nov/06 01:21
• Resolved: 01/Nov/06 01:21

Description

(Note that SerializationHandler is public in the Java sense, but is not a public API, so this issue is marking some internal development work that should be done).

The SerializationHandler interface, which is implemented by Xalan's serializers is a kitchen-sink of other interfaces. It includes these public APIs:
org.xml.sax.ContentHandler
org.xml.sax.ErrorHandler
org.xml.sax.ext.LexicalHandler
org.xml.sax.ext.DeclHandler

It appears that this interface:
org.xml.sax.DTDHandler
which has these two methods:
void notationDecl(String name, String publicId, String systemId);
void unparsedEntityDecl(String name, String publicId,
String systemId, String notationName);
should be added.

DeclHandler, that is already included in SerializationHandler has this method:
void elementDecl(String name, String model);

When an XML document like this one (from Xalan's expression02.xml testcase) is parsed, and serialized:
when parsing the XML input to the transformation:
<?xml version="1.0"?>
<!DOCTYPE doc [
<!NOTATION gif SYSTEM "../www.foo.com" >
<!ENTITY hatch-pic SYSTEM "../grafix/OpenHatch.gif" NDATA gif >
<!ELEMENT doc (#PCDATA)>
]>

the serializer handles the !ELEMENT just fine, and creates the surrounding !DOCTYPE, bucause the !ELEMENT is handled via the DeclHandler interface. However, there is no way to similarly serialize the !NOTATION or !ENTITY because these are handled via the DTDHandler interface.