Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 39433 invoked from network); 11 May 2005 14:21:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 May 2005 14:21:26 -0000 Received: (qmail 79786 invoked by uid 500); 11 May 2005 14:24:52 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 79602 invoked by uid 500); 11 May 2005 14:24:50 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 79445 invoked by uid 99); 11 May 2005 14:24:47 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of jayachandra@gmail.com designates 64.233.184.204 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.204) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 11 May 2005 07:24:47 -0700 Received: by wproxy.gmail.com with SMTP id 57so196180wri for ; Wed, 11 May 2005 07:20:56 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=a7oiP0aNFu0RRvOubMtrn31KQ481UN6qzNZxGPuhsCNmLO1p3EsjsBTYeKOevB28uvM5S1oKam6/LSN0l8L9TkE0TV5Oalsjp+hGI/5p0o5uCnOQ29gPWj0G1OIGI0AgAvpG4gQeAKJeAAW6NiQHIl3ws+aTV1jwZsjfS4K8o8A= Received: by 10.54.24.48 with SMTP id 48mr495473wrx; Wed, 11 May 2005 07:20:56 -0700 (PDT) Received: by 10.54.68.13 with HTTP; Wed, 11 May 2005 07:20:56 -0700 (PDT) Message-ID: <57023d130505110720440c40e1@mail.gmail.com> Date: Wed, 11 May 2005 19:50:56 +0530 From: jayachandra Reply-To: jayachandra To: axis-dev@ws.apache.org Subject: Fwd: [Axis2] Notes on underlying MXparser of OM In-Reply-To: <57023d13050511015247c1ea7a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20050511063204.73899.qmail@web31706.mail.mud.yahoo.com> <57023d13050511015247c1ea7a@mail.gmail.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Wanted to send it to the whole group. ---------- Forwarded message ---------- From: jayachandra Date: May 11, 2005 2:22 PM Subject: Re: [Axis2] Notes on underlying MXparser of OM To: Dasarath Weeratunge Hi Dasarath! At http://www.w3.org/XML/Test/#releases there is a downloadable XML Conformance Test suite available. In that under xmlconf/japanese directory there are a few xml files that have multibyte characters which you may want to use in your test case. Thanks Jayachandra On 5/11/05, Dasarath Weeratunge wrote: > Hi jayachandra, > > we are looking for some test cases to test one of our > pull parsers at LSF. What does your test cases contain > in terms of different encoding types? Our parser is > targeted for axis-c. > > --dasarath > > --- jayachandra wrote: > > Sorry! > > Just now found a solution on the stAX community how > > to make stAX > > parser understand the UTF encoding > > > > Jaya > > > > On 4/22/05, jayachandra > > wrote: > > > Alek! > > > The problem is that of localization. Businesses > > which publish local > > > language wsdl's can not be understood by Axis2. > > > The following (attached) XML file written in > > chinese/japanese couldn't > > > be parsed by the MXParser. Parsing threw a > > XMLStreamException saying > > > "start tag unexpected character \ub9" the moment > > it encountered a > > > foreign character. > > > Other than yahoo group is their some kind of > > mailing list for stAX > > > community? I've some problem using yahoogroups > > > > > > Thank you > > > Jayachandra > > > > > > On 4/21/05, Aleksander Slominski > > wrote: > > > > jayachandra wrote: > > > > > > > > >1. The MXParser doesn't seem to support the > > UTF-8 character set fully. > > > > >Japanese XML files weren't parsed properly. In > > future, this could > > > > >throw a serious problem. This can have it's > > effect on the SOAP message > > > > >processing of foreign web services. > > > > > > > > > > > > > > what is the problem? makes ure to send email > > about problems to > > > > http://groups.yahoo.com/group/stax_builders/ > > > > and file bug report(s) in bugzilla for StAX RI > > > > > > > (http://www.extreme.indiana.edu/bugzilla/buglist.cgi?product=3DSTAX) > > > > > > > > >2. The DTDParser inside MXParser was failing to > > understand the DTD > > > > >declaration line(s) of several (complex?) DTDs. > > Though this might not > > > > >seem as a problem if you look at the SOAP > > message processing part of > > > > >it, but certainly with such a behaviour > > complete XML infoset support > > > > >can not be given to our OM. > > > > > > > > > > > > > > are you actually testing validating or > > non-validating parser? > > > > requirement for non-validating parser are > > different in regard to DTDs. > > > > > > > > moreover DTDs are to be rejected by SOAP > > processor anyway ... > > > > > > > > thanks, > > > > > > > > alek > > > > > > > > -- > > > > The best way to predict the future is to invent > > it - Alan Kay > > > > > > > > > > > > > > -- > > > -- Jaya > > > > > > > > > > > > > > > -- > > -- Jaya > > > > Yahoo! Mail > Stay connected, organized, and protected. Take the tour: > http://tour.mail.yahoo.com/mailtour.html > > -- -- Jaya --=20 -- Jaya