ws-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryo Neyama <ney...@trl.ibm.co.jp>
Subject Re: Commit of the fixes and extensions (WAS Re: Request for two newlocus IDs)
Date Wed, 08 Nov 2000 15:00:25 GMT
Diane,

I didn't follow up your message. Sorry...
I perfectly agree with you.  JAXP would be appropriate for the
pluggability API.  I'm going to consider how it can be implemented in
Apache SOAP. Very thanks!

    Ryo Neyama @ IBM Research, Tokyo Research Laboratory
    Internet Technology
    neyama@trl.ibm.co.jp
    +81-46-215-4322 (Phone) / +81-46-273-7428 (FAX)

From: "Diane l. Davison" <Diane.Davison@oracle.com>
Subject: Re: Commit of the fixes and extensions (WAS Re: Request for two newlocus  IDs)
Date: Tue, 31 Oct 2000 14:21:32 -0800

> It would be great if the XML parser were pluggable.  Would you use JAXP as the
> pluggability API?
> (API for 1.0 is at http://java.sun.com/xml/docs/api/).
> 
> Diane
> 
> Ryo Neyama wrote:
> 
> >
> > There is another change proposed in the Fig.2  The current SOAP 2.0
> > implementation invokes a hard-coded XML parser.  We would like to
> > propose to make is replaceable with any other XML parsers.  This gives
> > programmers a freedom of parser choice.  Another advantage is that
> > this may be able to improve perfomance by eliminating multiple parser
> > calls because this is regarded as another kind of XML-in/DOM-out hook
> > and extension can be implemented as a part of parser (liaison)
> > functions.

Mime
View raw message