Hello,
I just scanned XNI interfaces to find out what is new and
found following issues:
- XMLAttributes.getName(int,QName)
it is odd, supported by JavaDoc talking about setting QName
- XMLAttributes.addAttribute(QName, String, String)
does not specify that the value is non-normalized (I suppose so)
also does not specify isSpecified() state after addition
- XMLAttributes.setValue(String)
probably as a side effect replaces non-normalized value
- XMLDocumentFragmentHandler.emptyElement(QName, XMLAttributes)
it is missing
- should not XMLDocumentHandler be derived from XMLDocumentFragmentHandler?
of both be derived from a new XMLContentHandler interface?
- I still miss definition of call order i.e. requirement for
proper nesting of startXXX() and endXXX() events so it would
be guaranteed that handler can use single stack for holding context
- startEntity(String,...) name can start with
'%' denoting parameter entity
'#' denoting character entity ref
- could be introduced XNIEntityIOException that
should be propagated if a component gets IOException
while scanning some external entity, so it would in
fact convert fatal error (IOException is handled even
more strict than fatal error) to error. Open issue
what to do with pipeline components, they probably
cannot rollback to state prior entity entering.
Comment welcome
Cc.
--
<address>
<a href="mailto:[EMAIL PROTECTED]";>Petr Kuzel</a> at Sun Microsystems
: <a href="http://xml.netbeans.org/";>XML module</a> and
: <a href="http://jini.netbeans.org/";>Jini</a> developer.</address>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
