--- Andy Clark <[EMAIL PROTECTED]> wrote:
> Jason Rizer wrote:
> > SAX2 ContentHandler interface.  Does anyone have
> any
> > idea for how many more versions xerces will
> continue
> > to support the SAX1 classes?
> 
> I'd like to remove them from Xerces2 when it's
> released
> but we have this pesky backwards compatibility
> thing...

Andy,

For what it's worth, I hope you don't remove them. 
I've put considerable effort into developing an XML
abstraction layer so that our software can run
transparently against whatever parser implementatin
the hosting App Server employs.  I know this sounds
like what DOM and JAXP already promise, but in
practice coding to these interfaces isn't enough (How
many times has the 'importNode' question been posted
to the list?) as the various parser implementations
running in production app servers vary in their level
of standards support.

Anyway, none of this is TOO bad on the DOM side.  I
just wrap the DOM interfaces in my own, and then when
I'm running against a DOM level one parser for
instance, I just call their native 'importNodeish'
method inside my importNode method wrapper.  The SAX
stuff is much tougher too handle though, in large part
because it implements callbacks which are a little
tougher to encapsulate in ones own code.  I actually
managed to get it ALMOST working by employing a couple
of layers of callbacks.  Still what finally sunk me
was the AttributeList -vs- Attributes issue.  So, now
I just call the SAX1 stuff for every parser (so far I
havn't found any that don't still support it) and
everything is good.  I apologize for rambling; I'm
half asleep at the moment but trying to wait for some
tests to finish.  

In summary, please don't do away with the SAX 1 stuff.

-Jason 

__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to