--- Lilantha Darshana <[EMAIL PROTECTED]> wrote:
> On 06/27/2005, Dasarath Weeratunge > [mailto:[EMAIL PROTECTED] wrote: > > >> > >> Would it be possible to do some XML 1.0 > compliancy & performance > check > >> before we decide? If you would able to make it > against > xerces/sax/expat > >> and JSR 173 - > >> > http://jcp.org/aboutJava/communityprocess/final/jsr173/index.html > >> It would be great. > > > >I'm not sure why this is necessary at this point > since this is > >basically to get the src tree in sync with the > latest code-- of course > >the more test we do the better it is but I'm not > very keen on > >performance tests even before we get the parser > going. The tests that > >we have prepared are to test the functionality and > not intended to > >compare performance. Further though I have revised > the basic state > >machine several times the encoding part is still > very fresh and there > >is a lot that can be improved. I'm confident that > given time Guththila > >pick up. > > > My assumption was impl. of Guththila has at least > 70-80% completed. > With this assumption, if ppl want to use the XML > pull API, and address > real world problem with doc/lit encoding in their > service handlers they > require > compliance XML parser. o/w we need to suggest them > to use some other XML > parser in their service/client handlers and use this > one only > internally. Full XML compliance will take a long time to come if ever since that would mean support for DTDs, compiler directives etc. But we do not need many of these for Soap. We do need to support entity references. So it would be a good idea to run the W3C Xml test suit and categorise which tests fail and of those that fail which ones we need to support. Then we can clearly point users to a list of supported/unsupported features. Thanks --dasarath > > Anyway, if you think - although it's not compliance > at this moment. > Since it is the next version of txpp/tspp, we may > proceed and get rid of > > obsolete code and improve this one instead. > > +1 from me. > > Cheers, > -Lilantha > > > > > Where can we see the currently impl code? > > > > Thanks > > -Lilantha > > > > > > -----Original Message----- > > From: Dasarath Weeratunge > [mailto:[EMAIL PROTECTED] > > Sent: Sunday, June 26, 2005 12:34 PM > > To: [email protected] > > Subject: Moving Guththila to Axis C++ src tree > > > > Hi, > > > > How about moving Guththila code into the Axis C++ > src tree? > > > > Dinesh is trying to implement XMLParser interface > in XMLParser.h for > > Guththila. At the moment the code that we have in > the src tree > > **/xml/tspp/ and **/xml/txpp/ are both old > versions of Guththila > > written by Susantha, Damitha and my self. > > > > Dinesh's code cannot be integrated with either one > of these since its > a > > different fork of tspp altogether. > > > > What I propose therefore is that we take off this > code and substitute > > Dinesh's code in their place. We can create a new > subdirectory > > `guththila' > > at the same level as `xerces' and `expat' under > **/xml/ and delete > > old subdirectories `tspp' and `txpp'. > > > > Dinesh's code builds on tspp code and implements a > full StAX parser > > with the exception of DTD's and a few other > constructs rarely used in > > Soap processing. It also supports character > encoding schemes and comes > > with a set of test cases. The encoding related > code in the new code > base > > has > > been completely rewritten unlike earlier (see > **/xml/txpp/) where we > > tried > > to reuse code from expat. We also improved the > tokenizing code and API > > to be in > > line with StAX. > > > > IMHO cleaning up the src tree would make life > easier for us who are > > working on Guththila since then we can directly > commit our code to the > > CVS. > > > > Regards, > > --dasarath > > > > > > > > > > _______________ > > Siebel > > IT'S ALL ABOUT THE CUSTOMER > > Visit www.siebel.com > > > > This e-mail message is for the sole use of the > intended recipient(s) > and contains confidential and/or privileged > information belonging to > Siebel Systems, Inc. or its customers or partners. > Any unauthorized > review, use, copying, disclosure or distribution of > this message is > strictly prohibited. If you are not an intended > recipient of this > message, please contact the sender by reply e-mail > and destroy all soft > and hard copies of the message and any attachments. > Thank you for your > cooperation. > > > > > > > > > ____________________________________________________ Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football http://football.fantasysports.yahoo.com
