axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <sanj...@watson.ibm.com>
Subject Re: JDom
Date Sun, 04 Mar 2001 12:25:42 GMT
Doesn't this mean we can no longer use JAXP as a parser pluggability
mechanism? 

My understanding was that Axis was going to remain representation 
independent at its core and specific handlers may do whatever they
wish. Did that change at the F2F? [Can someone please summarize
the F2F activities?]

What about being purely based on SAX at least for like the RPC
handler? I understand header semantics may not allow streaming, 
however, life without a streaming based impl is bound to be
slow IMO. For RPC implemented services, my intuition is that 
there will be lots of case which do not have any headers .. thus
a pure streaming impl will be screaming on those cases.

Sanjiva.

----- Original Message ----- 
From: "Doug Davis" <dug@us.ibm.com>
To: <axis-dev@xml.apache.org>
Sent: Saturday, March 03, 2001 6:54 PM
Subject: JDom


> FYI - I switched AXIS to use JDom instead of Xerces/DOM.
> Changes were actually pretty minor and painless.  8-)
> So, now we'll see if it actually makes things faster...
> -Dug
> 


Mime
View raw message