[jdom-interest] SAXHandler's Stack to be protected ?
jozart at csi.com
Mon Aug 20 22:43:07 PDT 2001
Paul Libbrecht writes:
> De-private-ising the stack member (or having a "currentElement"
> accessor) would allow me to stick to this very economic philosophy.
Just keep in mind, as more of the implementation is exposed, that JSR-102 is
not just an implementation, but also a specification. That is, a subclass
that conforms to the specification should interoperate with any
(I've also suggested that an object serialized in one implementation should
deserialize in another implementation, but since SAXHandler isn't
Serializable, that's neither here nor there.)
--- original message ---
From: Paul Libbrecht paul at ags.uni-sb.de
Date: Tue, 21 Aug 2001 01:41:42 +0200
In my ongoing efforts for elements with locators, I'd need the
org.jdom.input.SAXHandler's stack variable to be protected so as to allow
me to pre- post-process the element being built while subclassing
As far as I understand the SAX building mechanism of JDOM, I dare say
SAXHandler is the only object that seems to need to be created new at each
De-private-ising the stack member (or having a "currentElement" accessor)
would allow me to stick to this very economic philosophy.
More information about the jdom-interest