[xerces2] Note to current XNI state

[Petr Kuzel <Pe...@sun.com>]

Hello,

  we are using XNI as it exists in alpha. We found there a problem
with entity callbacks. Consider following demo DTD fragments:

a)

  <!ENTITY % ent "ANY">
  <!ELEMENT e %ent;>

b)

  <!ENTITY % ent " ">
  %ent;
  <!ELEMENT e ANY>

both produces:

  entityDecl(..);
  startEntity("ent",...);
  ...
  endEntity("ent");
  elementDecl(..);

The problem is that handler gets information about entities
in markup in the same way as for grammar entities. It is another
pros why to split callbacks in DTD handler as latest XNI suggests.

  Cc.

-- 
<address>
<a href="mailto:pkuzel@netbeans.com">Petr Kuzel</a>, Sun Microsystems
: <a href="http://www.sun.com/forte/ffj/ie/">Forte Tools</a>
: XML and <a href="http://jini.netbeans.org/">Jini</a> modules</address>

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org

Re: [xerces2] Note to current XNI state

[Andy Clark <an...@apache.org>]

Petr Kuzel wrote:
>   we are using XNI as it exists in alpha. We found there a problem
> with entity callbacks. Consider following demo DTD fragments:

This is exactly why we were working on new DTD handler
interfaces so that more meaningful information could
be derived. But I haven't heard any concensus from the
community as to whether this is the right way to go. 

I don't like the way that the number of methods explodes
in order to handle this feature for a small segment of
the Xerces user base (primarilly editor writers). 

Can we come to some agreement on this soon? Why is
everyone so quiet these days?

-- 
Andy Clark * IBM, TRL - Japan * andyc@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org