Neeraj Bajaj wrote:
> I feel currently XMLDTDHandler:internalEntityDecl() is passing non-Normalized
> value to the application or am i not clear with "normalized value of entity" ?
Actually, it's not. For example:
<!ENTITY % one 'b'>
<!ENTITY % two 'A%one;C'>
The callbacks would be the following:
internalEntityDecl("%one", "b");
internalEntityDecl("%two", "AbC");
Whereas, adding the non-normalized value in the callback would
look like this:
internalEntityDecl("%one", "b", "b");
internalEntityDecl("%two", "AbC", "A%one;C");
> > (?) Should Handler/Source/Filter Be in Same Package
>
> i would like to see them in different packages.
> what about scanner interfaces ?
The current separation is as follows:
package org.apache.xerces.xni
interface XMLDocumentHandler
interface XMLDTDHandler
interface XMLDTDContentModelHandler
interface XMLDocumentFragmentHandler*
package org.apache.xerces.xni.parser
interface XMLDocumentSource
interface XMLDocumentScanner
interface XMLDTDSource
interface XMLDTDContentModelSource
interface XMLDTDScanner
* There is no corresponding XMLDocumentFragmentSource
for the XMLDocumentFragmentHandler interface.
So we have scanner interfaces but they are grouped in the
"parser" package. To me this sorta makes sense because
they are related to the parsing pipeline and aren't
strictly needed for communicating the streaming document
information set. However, adding three additional
interfaces seems to bloat the package more...
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
