From swansonlinda@example.org Tue Jan 2 09:53:58 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 79691 invoked from network); 2 Jan 2001 09:53:58 -0000 Received: from knox.decisionsoft.com (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 09:53:58 -0000 Received: from tugela.dsl.local ([83.161.120.155] helo=tugela.dsl.net ident=irr) by knox.decisionsoft.com with esmtp (Exim 3.16 #1) id 14DP6d-00035D-00 for swansonlinda@example.org; Tue, 02 Jan 2001 10:55:51 +0000 Date: Tue, 2 Jan 2001 09:53:23 +0000 (GMT) From: Ian Roberts <swansonlinda@example.org> X-Sender: swansonlinda@example.org To: swansonlinda@example.org Subject: Re: Stubbon Error: Validation error for attribute In-Reply-To: <swansonlinda@example.org> Message-ID: <swansonlinda@example.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Sat, 30 Dec 2000, Dream Catcher wrote: > 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4Users.xsd > > <xsd:schema xmlns:xsd = "http://www.w3.org/1999/XMLSchema-instance"> This should be xmlns:xsd="http://www.w3.org/1999/XMLSchema". Everything else looks OK at first glance. Ian -- Ian Roberts | swansonlinda@example.org DecisionSoft Ltd. | http://www.decisionsoft.com/ From swansonlinda@example.org Tue Jan 2 13:32:22 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 27175 invoked from network); 2 Jan 2001 13:32:22 -0000 Received: from unknown (HELO outbound.silknet.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 13:32:22 -0000 Received: from mht-ex1.silknet.com ([83.161.120.155]) by outbound.silknet.com with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 2 Jan 2001 08:31:19 -0500 Received: by mht-ex1.silknet.com with Internet Mail Service (5.5.2653.19) id <CD1QLV19>; Tue, 2 Jan 2001 08:31:35 -0500 Message-ID: <swansonlinda@example.org> From: Ed Staub <swansonlinda@example.org> To: "'swansonlinda@example.org'" <swansonlinda@example.org> Subject: RE: [Xerces2] Survey Date: Tue, 2 Jan 2001 08:31:35 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N 1.) Xerces 1.x 2.) n/a 3.) Standards compliance, Performance: speed 4.) Followed the Xerces2 discussion on the mailing list Read the online documentation located at http://www.apache.org/~andyc/xerces2/ 5.) Not a priority at this time. 6.) Wait and see 7.) n/a 8.) n/a 9.) probably not 10.) (there's a tie for 1st place) > [1 ] Grammar access > [2 ] Grammar caching > [1 ] Write validation: the ability to apply a grammar to > a document after parsing. For example, validate a DOM > tree after editing -Ed Staub Kana Communications, Inc. From swansonlinda@example.org Tue Jan 2 14:12:15 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 49302 invoked from network); 2 Jan 2001 14:12:15 -0000 Received: from lukla.sun.com (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 14:12:15 -0000 Received: from gw.netbeans.com ([83.161.120.155]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA01065 for <swansonlinda@example.org>; Tue, 2 Jan 2001 07:12:11 -0700 (MST) Received: from homesrv.netbeans.com (homesrv.netbeans.com [83.161.120.155]) by gw.netbeans.com (8.9.3/8.9.3) with ESMTP id PAA15849 for <swansonlinda@example.org>; Tue, 2 Jan 2001 15:12:10 +0100 Received: from netbeans.com (IDENT:swansonlinda@example.org [83.161.120.155]) by homesrv.netbeans.com (8.9.3/8.9.3) with ESMTP id PAA29114 for <swansonlinda@example.org>; Tue, 2 Jan 2001 15:12:06 +0100 Sender: swansonlinda@example.org Message-ID: <swansonlinda@example.org> Date: Tue, 02 Jan 2001 15:12:05 +0100 From: Petr Kuzel <swansonlinda@example.org> Organization: Sun Microsystems X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Xerces2 Development <swansonlinda@example.org> Subject: [Xerces2] packaging Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hello, I have question about Xerces2 packaging. It seems to me that having both versions of Xerces at classpath at same time may cause problems. There are some conflicting classes defined in both versions of Xerces. org.apache.xerces.parsers.SAXParser is such case. Public methods have changed in incompatible manner. IFAIK Java binary compatibility and Package Versioning specs does not allow it. I would suggest repackaging the parser into org.apache.xerces2 subpackages or adhere to Package Versioning specs. From may point of view a repackaging is preffered as it allows to have both versions at classpath and switch implementations dynamically. Another packaging issue is bound to deployment stage. I am not sure whether it is a good idea to bundle implementation and specification into single jar. I mean that SAX, DOM and JAXP specs. Some problems may appear if multiple versions of them appear at classpath as only SAX allows to have both versions at classpath (besides DOM L2 Java mapping does not follow the versioning specs as it adds methods into public interfaces instead of extending them). I would prefer a zip or tarball containing four jars. Comments are welcome Ccc -- <address> <a href="mailto:swansonlinda@example.org">Petr Kuzel</a>, Sun Microsystems : <a href="http://www.sun.com/forte/ffj/ie/">Forte Tools</a> : XML and <a href="http://jini.netbeans.org/">Jini</a> modules</address> From swansonlinda@example.org Tue Jan 2 14:29:43 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 57602 invoked from network); 2 Jan 2001 14:29:43 -0000 Received: from unknown (HELO posiedon.ellora.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 14:29:43 -0000 Received: by posiedon.ellora.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62) id <swansonlinda@example.org>; Tue, 2 Jan 2001 09:40:44 -0500 Message-ID: <swansonlinda@example.org> From: Keith Jensen <swansonlinda@example.org> To: "'swansonlinda@example.org'" <swansonlinda@example.org> Subject: RE: [Xerces2] Survey Date: Tue, 2 Jan 2001 09:40:43 -0500 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > -----Original Message----- > From: Andy Clark [mailto:swansonlinda@example.org] > Sent: Friday, December 29, 2000 12:46 AM > To: swansonlinda@example.org > Subject: [Xerces2] Survey > > > Well, the holidays have slowed everything down so I think that > now is a good time to take a survey from the Xerces community > about Xerces2. So, if you have the time, please respond to this > message with your responses. > > XERCES2 SURVEY > > Section 1: Usage > > 1) What parser are you using in your application? Select one > parser by putting an 'X' in the box next to your choice. If > you have a hybrid application that uses more than one parser, > select the most important parser for your application. > > [X] Xerces 1.x > [ ] Xerces 1.x packaged with Xalan > [ ] Xerces 2.x > [ ] XML4J 1.x/2.x > [ ] Crimson > [ ] _________________________ > > 2) If you did NOT select Xerces in question 1, what were your > reasons for not using Xerces in your application? Select all > that apply. > > [ ] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [ ] Specialized API (What features?) > [ ] License > [ ] _________________________ > > 3) If you DID select Xerces in question 1, what were your > reasons for using Xerces in your application? Select all > that apply. > > [X] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [ ] Specialized API (What features?) > [X] License > [ ] _________________________ > > Section 2: Xerces2 > > 4) What is your level of knowledge of Xerces2? Select all > that apply. > > [X] Followed the Xerces2 discussion on the mailing list > [ ] Read the online documentation located at > http://www.apache.org/~andyc/xerces2/ > [ ] Reviewed the Xerces Native Interface (XNI) > [ ] Downloaded Xerces 2.0.0 (alpha) or extracted and built > the source from CVS > [ ] Tried Xerces2 in an application > > 5) If you have heard of Xerces2 but have NOT tried it, what > would you say is the primary reason? Select only one answer. > > [ ] Current parser works fine > [ ] No time to try > [X] Does not support XML Schema yet and no production versa. > > 6) Despite your current use of Xerces2, do you plan on moving > your application to using Xerces2 when a production version > becomes available? Select only one answer. > > [X] Yes (If it works as well as Xerces1.) > [ ] Wait and see > [ ] No > > 7) If you have reviewed XNI, what is your impression? Select > only one answer. > > [ ] Love it > [ ] Like it > [ ] Could be better > [ ] Hate it > [ ] Don't care > > 8) If you answered "Could be better" or "Hate it" to question > 6, what suggestions do you have? Please site specific > interfaces, methods, etc. > > 9) Do you plan on contributing to Xerces2? In what way? > > [X] Yes > [ ] Source > [ ] Samples > [ ] Documentation > [X] Build/Testing > I will test it in my application and report any bugs that > are encountered. > [ ] No > > Section 3: Wish List > > 10) What are the features that you would like to see implemented > in Xerces2? Rank the three most important to you by putting > a '1', '2', and '3' in the boxes next to your choices, where > '1' is the most important and '3' is the least important > among your choices. > > [ ] Grammar access > [ ] Grammar caching > [ ] Write validation: the ability to apply a grammar to > a document after parsing. For example, validate a DOM > tree after editing > [1] Complete support for XML Schema CR/R. > [2] Make the xsd:all construct work efficiently. > [3] Fast performance and minimize bugs. > I want to use Xerces in a real production system with full > support for XML Schema CR/R, efficient validation, and as bug-free as > possible. This is needed prior to adding bells and whistles for > non-standard proprietary features, which I will avoid using > because they are non-standard and will hamper my ability to evaluate > parsers on an on-going basis to ensure I am using best-of-breed > software. > > -- > Andy Clark * IBM, TRL - Japan * swansonlinda@example.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: swansonlinda@example.org > For additional commands, e-mail: swansonlinda@example.org > > From swansonlinda@example.org Tue Jan 2 14:36:21 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 67150 invoked from network); 2 Jan 2001 14:36:21 -0000 Received: from h-205-217-237-47.netscape.com (HELO netscape.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 14:36:21 -0000 Received: from dredd.mcom.com (dredd.mcom.com [83.161.120.155]) by netscape.com (8.10.0/8.10.0) with ESMTP id f02ERA311898 for <swansonlinda@example.org>; Tue, 2 Jan 2001 06:27:10 -0800 (PST) Received: from vortexlnx1 ([83.161.120.155]) by dredd.mcom.com (Netscape Messaging Server 4.15 dredd Jun 22 2000 16:29:39) with SMTP id G6JHVS00.ABU for <swansonlinda@example.org>; Tue, 2 Jan 2001 06:35:52 -0800 From: "Toby H Ferguson" <swansonlinda@example.org> To: <swansonlinda@example.org> Subject: RE: About XML encoding Date: Tue, 2 Jan 2001 06:35:51 -0800 Message-ID: <swansonlinda@example.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01C07486.401BFE70" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <swansonlinda@example.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N ------=_NextPart_000_000A_01C07486.401BFE70 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: 7bit Suk Tae Kyung, you *must* use an encoding in which all your various languages can be encoded if they're all going to be in the same file - however, you can break up the file into different files, each with their own encoding, and that way get around your problem with UTF-8 Why do you think the UTF-8 data is broken? THere are not many editors which understand UTF-8 - I normally read UTF-8 documents using browsers, which are UTF-8 aware. Toby -----Original Message----- From: Suk Tae Kyung [mailto:swansonlinda@example.org] Sent: Tuesday, December 26, 2000 10:50 PM To: Xerces Subject: Q:About XML encoding Hi, Xerces Developers. I have a question on the encoding of XML. Although this question is not on Xerces, it has relation to Xerces. To specify encoding info, one should write xml like this... <?xml version="1.0" encoding="some encoding" ?> <~~~> </~~~> If i use Korean data, i should specify "euc-kr" encoding. But if i use Korean and Chinease and Japanese in one XML, which encoding should i set? It would be possible that all data is transformed into UTF-8 and specifying "UTF-8" as encoding. But this method is not good because all data is transformed into UTF-8 first and this data is not swansonlinda@example.org.(data seems to be broken) Does any one have good idea? Thanks in advance. Regards. Suk Tae Kyung ------=_NextPart_000_000A_01C07486.401BFE70 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content=3D"text/html; charset=3Dks_c_5601-1987" = http-equiv=3DContent-Type> <META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = class=3D267282414-02012001>Suk=20 Tae Kyung,</SPAN></FONT></DIV> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 class=3D267282414-02012001></SPAN></FONT>&nbsp;</DIV> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = class=3D267282414-02012001>you=20 *must* use an encoding in which all your various languages can be = encoded if=20 they're all going to be in the same file - however, you can break up the = file=20 into different files, each with their own encoding, and that way get = around your=20 problem with UTF-8</SPAN></FONT></DIV> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 class=3D267282414-02012001></SPAN></FONT>&nbsp;</DIV> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN = class=3D267282414-02012001>Why do=20 you think the UTF-8 data is broken? THere are not many editors which = understand=20 UTF-8 - I normally read UTF-8 documents using browsers, which are UTF-8=20 aware.</SPAN></FONT></DIV> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 class=3D267282414-02012001></SPAN></FONT>&nbsp;</DIV> <DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20 class=3D267282414-02012001>Toby</SPAN></FONT></DIV> <BLOCKQUOTE style=3D"MARGIN-RIGHT: 0px"> <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT = face=3DTahoma=20 size=3D2>-----Original Message-----<BR><B>From:</B> Suk Tae Kyung=20 [mailto:swansonlinda@example.org]<BR><B>Sent:</B> Tuesday, December 26, = 2000 10:50=20 PM<BR><B>To:</B> Xerces<BR><B>Subject:</B> Q:About XML=20 encoding<BR><BR></DIV></FONT> <DIV><FONT size=3D2> <DIV><FONT size=3D2>Hi, Xerces Developers. I have a question on the = encoding of=20 XML.</FONT></DIV> <DIV>Although this&nbsp;question is not&nbsp;on Xerces, it has = relation to=20 Xerces.</DIV> <DIV>&nbsp;</DIV> <DIV>&nbsp;</DIV> <DIV><FONT size=3D2>To specify encoding info, one should write xml = like=20 this...</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT size=3D2>&nbsp;&nbsp; &lt;?xml version=3D"1.0" = encoding=3D"some encoding"=20 ?&gt;</FONT></DIV> <DIV><FONT size=3D2>&nbsp;&nbsp; &lt;~~~&gt;</FONT></DIV> <DIV><FONT size=3D2>&nbsp;&nbsp; &lt;/~~~&gt;</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT size=3D2>If i use Korean data, i should specify "euc-kr" = encoding.=20 But</FONT></DIV> <DIV><FONT size=3D2>if i use Korean and Chinease and Japanese in one = XML, which=20 encoding </FONT></DIV> <DIV><FONT size=3D2>should i set? </FONT></DIV> <DIV><FONT size=3D2>It would be possible&nbsp;that&nbsp;all data is = transformed=20 into UTF-8 and specifying "UTF-8"</FONT></DIV> <DIV><FONT size=3D2>as encoding. But this method is not good because = all data is=20 transformed into UTF-8</FONT></DIV> <DIV><FONT size=3D2>first and this data is not swansonlinda@example.org.(data = seems to be=20 broken)</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT size=3D2>Does any one have good idea?</FONT></DIV> <DIV><FONT size=3D2>Thanks in advance.</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT size=3D2>Regards.</FONT></DIV> <DIV>&nbsp;</DIV> <DIV><FONT size=3D2>Suk Tae=20 Kyung</FONT></DIV></FONT></DIV></BLOCKQUOTE></BODY></HTML> ------=_NextPart_000_000A_01C07486.401BFE70-- From swansonlinda@example.org Tue Jan 2 14:40:38 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 70375 invoked from network); 2 Jan 2001 14:40:38 -0000 Received: from lukla.sun.com (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 14:40:38 -0000 Received: from gw.netbeans.com ([83.161.120.155]) by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id HAA12433 for <swansonlinda@example.org>; Tue, 2 Jan 2001 07:40:38 -0700 (MST) Received: from homesrv.netbeans.com (homesrv.netbeans.com [83.161.120.155]) by gw.netbeans.com (8.9.3/8.9.3) with ESMTP id PAA16105 for <swansonlinda@example.org>; Tue, 2 Jan 2001 15:40:37 +0100 Received: from netbeans.com (IDENT:swansonlinda@example.org [83.161.120.155]) by homesrv.netbeans.com (8.9.3/8.9.3) with ESMTP id PAA02500 for <swansonlinda@example.org>; Tue, 2 Jan 2001 15:40:37 +0100 Sender: swansonlinda@example.org Message-ID: <swansonlinda@example.org> Date: Tue, 02 Jan 2001 15:40:37 +0100 From: Petr Kuzel <swansonlinda@example.org> Organization: Sun Microsystems X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: swansonlinda@example.org Subject: Re: [Xerces2] Survey References: <swansonlinda@example.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Andy Clark wrote: > > Well, the holidays have slowed everything down so I think that > now is a good time to take a survey from the Xerces community > about Xerces2. So, if you have the time, please respond to this > message with your responses. > > XERCES2 SURVEY > > Section 1: Usage > > 1) What parser are you using in your application? Select one > parser by putting an 'X' in the box next to your choice. If > you have a hybrid application that uses more than one parser, > select the most important parser for your application. > > [ ] Xerces 1.x > [ ] Xerces 1.x packaged with Xalan > [ ] Xerces 2.x > [ ] XML4J 1.x/2.x > [ ] Crimson > [X] own parser (patched Crimson) > > 2) If you did NOT select Xerces in question 1, what were your > reasons for not using Xerces in your application? Select all > that apply. > > [ ] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [X] Specialized API (What features?) all Crimson extensions to SAX plus entity ref., declaration, ... notifications simply trying to achieve round trip: text -> internal structure -> "same" text > [ ] License > [X] We need to do a code customization > > 3) If you DID select Xerces in question 1, what were your > reasons for using Xerces in your application? Select all > that apply. > > [ ] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [ ] Specialized API (What features?) > [ ] License > [ ] _________________________ > > Section 2: Xerces2 > > 4) What is your level of knowledge of Xerces2? Select all > that apply. > > [X] Followed the Xerces2 discussion on the mailing list > [X] Read the online documentation located at > http://www.apache.org/~andyc/xerces2/ > [X] Reviewed the Xerces Native Interface (XNI) > [X] Downloaded Xerces 2.0.0 (alpha) or extracted and built > the source from CVS > [X] Tried Xerces2 in an application > > 5) If you have heard of Xerces2 but have NOT tried it, what > would you say is the primary reason? Select only one answer. > > [ ] Current parser works fine > [ ] No time to try > [ ] _________________________ > > 6) Despite your current use of Xerces2, do you plan on moving > your application to using Xerces2 when a production version > becomes available? Select only one answer. > > [X] Yes > [ ] Wait and see > [ ] No > > 7) If you have reviewed XNI, what is your impression? Select > only one answer. > > [ ] Love it > [ ] Like it > [X] Could be better > [ ] Hate it > [ ] Don't care > > 8) If you answered "Could be better" or "Hate it" to question > 6, what suggestions do you have? Please site specific > interfaces, methods, etc. some notification methods missing. E.g. in conditional section would be an application notified about its content by say a String representing it. public void ignoredConditionalContent(String); > > 9) Do you plan on contributing to Xerces2? In what way? > > [X] Yes > [ ] Source > [ ] Samples > [ ] Documentation > [ ] Build/Testing > [ ] No > > Section 3: Wish List > > 10) What are the features that you would like to see implemented > in Xerces2? Rank the three most important to you by putting > a '1', '2', and '3' in the boxes next to your choices, where > '1' is the most important and '3' is the least important > among your choices. > > [ ] Grammar access > [ ] Grammar caching > [ ] Write validation: the ability to apply a grammar to > a document after parsing. For example, validate a DOM > tree after editing > [1] Package versioning compatability > [2] XNI improvement and standartization > [ ] _________________________ > Ccc -- <address> <a href="mailto:swansonlinda@example.org">Petr Kuzel</a>, Sun Microsystems : <a href="http://www.sun.com/forte/ffj/ie/">Forte Tools</a> : XML and <a href="http://jini.netbeans.org/">Jini</a> modules</address> From swansonlinda@example.org Tue Jan 2 14:51:56 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 83890 invoked from network); 2 Jan 2001 14:51:56 -0000 Received: from bounce.harvard.net (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 14:51:56 -0000 Received: from mail.ime.net (ime.net [83.161.120.155]) by bounce.harvard.net (8.11.0/8.10.1) with ESMTP id f02EpuK26263 for <swansonlinda@example.org>; Tue, 2 Jan 2001 09:51:56 -0500 Received: from ntplx.net (4109-maine-56k.ime.net [83.161.120.155]) by mail.ime.net (8.10.1/8.9.3) with ESMTP id f02EptH29278 for <swansonlinda@example.org>; Tue, 2 Jan 2001 09:51:55 -0500 Message-ID: <swansonlinda@example.org> Date: Tue, 02 Jan 2001 09:51:55 -0500 From: Frank Griffin <swansonlinda@example.org> X-Mailer: Mozilla 4.61 [en] (OS/2; U) X-Accept-Language: en MIME-Version: 1.0 To: swansonlinda@example.org Subject: Re: [Xerces2] Survey References: <swansonlinda@example.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Andy Clark wrote: > Well, the holidays have slowed everything down so I think that > now is a good time to take a survey from the Xerces community > about Xerces2. So, if you have the time, please respond to this > message with your responses. > > XERCES2 SURVEY > > Section 1: Usage > > 1) What parser are you using in your application? Select one > parser by putting an 'X' in the box next to your choice. If > you have a hybrid application that uses more than one parser, > select the most important parser for your application. > > [x] Xerces 1.x > [ ] Xerces 1.x packaged with Xalan > [ ] Xerces 2.x > [ ] XML4J 1.x/2.x > [ ] Crimson > [ ] _________________________ > > 2) If you did NOT select Xerces in question 1, what were your > reasons for not using Xerces in your application? Select all > that apply. > > [ ] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [ ] Specialized API (What features?) > [ ] License > [ ] _________________________ > > 3) If you DID select Xerces in question 1, what were your > reasons for using Xerces in your application? Select all > that apply. > > [x] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [ ] Specialized API (What features?) > [x] License > [] _________________________ > > Section 2: Xerces2 > > 4) What is your level of knowledge of Xerces2? Select all > that apply. > > [x] Followed the Xerces2 discussion on the mailing list > [ ] Read the online documentation located at > http://www.apache.org/~andyc/xerces2/ > [ ] Reviewed the Xerces Native Interface (XNI) > [ ] Downloaded Xerces 2.0.0 (alpha) or extracted and built > the source from CVS > [ ] Tried Xerces2 in an application > > 5) If you have heard of Xerces2 but have NOT tried it, what > would you say is the primary reason? Select only one answer. > > [ ] Current parser works fine > [x] No time to try > [ ] _________________________ > > 6) Despite your current use of Xerces2, do you plan on moving > your application to using Xerces2 when a production version > becomes available? Select only one answer. > > [x] Yes > [ ] Wait and see > [ ] No > > 7) If you have reviewed XNI, what is your impression? Select > only one answer. > > [ ] Love it > [ ] Like it > [ ] Could be better > [ ] Hate it > [ ] Don't care > > 8) If you answered "Could be better" or "Hate it" to question > 6, what suggestions do you have? Please site specific > interfaces, methods, etc. > > 9) Do you plan on contributing to Xerces2? In what way? > > [x] Yes > [x] Source > [ ] Samples > [ ] Documentation > [x] Build/Testing > [ ] No > > Section 3: Wish List > > 10) What are the features that you would like to see implemented > in Xerces2? Rank the three most important to you by putting > a '1', '2', and '3' in the boxes next to your choices, where > '1' is the most important and '3' is the least important > among your choices. > > [1] Grammar access > [2] Grammar caching > [ ] Write validation: the ability to apply a grammar to > a document after parsing. For example, validate a DOM > tree after editing > [3] Add an interface layer which combines the ease of DOM ("I know what I want") with the memory overhead of SAX (I'm reading the document sequentially and don't need random or backwards access). Since Xerces can already defer node-building, could this be as easy as a "sequential DOM" option, which frees nodes for GC once they've been read or passed ? > [ ] _________________________ > [ ] _________________________ From swansonlinda@example.org Tue Jan 2 16:10:03 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 51753 invoked from network); 2 Jan 2001 16:10:03 -0000 Received: from notes.totalsystem.com (HELO internet?notes1.totalsystem.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 16:10:03 -0000 Received: from notes.dots.com ([83.161.120.155]) by mk-notesmail1.totalsystem.net (Lotus Domino Release 5.0.3) with ESMTP id 2001010211104209:1887 ; Tue, 2 Jan 2001 11:10:42 -0500 Received: from dots1024 ([83.161.120.155]) by notes.dots.com (Lotus Domino Release 5.0.3) with SMTP id 2001010211081551:1828 ; Tue, 2 Jan 2001 11:08:15 -0500 From: "Scott Carter" <swansonlinda@example.org> To: <swansonlinda@example.org> Subject: Validation with SAX Date: Tue, 2 Jan 2001 11:18:37 -0500 Message-ID: <swansonlinda@example.org> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal X-MIMETrack: Itemize by SMTP Server on notes/Dotsconnect(Release 5.0.3 |March 21, 2000) at 01/02/2001 11:08:15 AM, Serialize by Router on notes/Dotsconnect(Release 5.0.3 |March 21, 2000) at 01/02/2001 11:08:16 AM, Serialize complete at 01/02/2001 11:08:16 AM, Itemize by SMTP Server on MK-NOTESMAIL1/TotalSystem(Release 5.0.3 |March 21, 2000) at 01/02/2001 11:10:42 AM, Serialize by Router on Internet_Notes1/TSYSInternet(Release 5.0.3 |March 21, 2000) at 01/02/2001 11:05:16 AM, Serialize complete at 01/02/2001 11:05:16 AM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N I have a simple question that I hope someone can answer. I'm trying to do a validating parse of a series of documents using SAX, but the problem I'm having is that the parser doesn't appear to be validating. I'm using JAXP to call the parser and I'm setting the validate option as follows: RequestHandler handler = new RequestHandler(); SAXParser saxParser = factory.newSAXParser(); factory.setValidating(true); saxParser.parse(docStream, handler); Any ideas why this is happening? From swansonlinda@example.org Tue Jan 2 16:37:44 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 70458 invoked from network); 2 Jan 2001 16:37:44 -0000 Received: from e31.co.us.ibm.com (HELO e31.bld.us.ibm.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 16:37:44 -0000 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [83.161.120.155]) by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id LAA28684 for <swansonlinda@example.org>; Tue, 2 Jan 2001 11:31:06 -0500 From: swansonlinda@example.org Received: from d25ml04.torolab.ibm.com (d25ml04.torolab.ibm.com [83.161.120.155]) by westrelay02.boulder.ibm.com (8.11.0m3/NCO v4.95) with ESMTP id f02Gbb0151888 for <swansonlinda@example.org>; Tue, 2 Jan 2001 09:37:37 -0700 Importance: Normal Subject: Re: Validation with SAX To: swansonlinda@example.org X-Mailer: Lotus Notes Release 5.0.4a July 24, 2000 Message-ID: <swansonlinda@example.org> Date: Tue, 2 Jan 2001 11:37:34 -0500 X-MIMETrack: Serialize by Router on D25ML04/25/M/IBM(Release 5.0.4a |July 24, 2000) at 01/02/2001 11:37:36 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hi Scott, Looks like you've got one of the more popular errors in these parts: you haven't declared an ErrorHandler. So you need to write a class implementing ErrorHandler to handle exceptions thrown by the SAX Parser and register it using the setErrorHandler method; i.e., append saxParser.setErrorHandler(handler); to this code snippet. You can look at the ErrorHandler.java interface in the org.xml.sax package. Hope that helps, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 2209615571, T/L 778-3519 E-mail: swansonlinda@example.org "Scott Carter" <swansonlinda@example.org> on 01/02/2001 11:18:37 AM Please respond to swansonlinda@example.org To: <swansonlinda@example.org> cc: Subject: Validation with SAX I have a simple question that I hope someone can answer. I'm trying to do a validating parse of a series of documents using SAX, but the problem I'm having is that the parser doesn't appear to be validating. I'm using JAXP to call the parser and I'm setting the validate option as follows: RequestHandler handler = new RequestHandler(); SAXParser saxParser = factory.newSAXParser(); factory.setValidating(true); saxParser.parse(docStream, handler); Any ideas why this is happening? --------------------------------------------------------------------- To unsubscribe, e-mail: swansonlinda@example.org For additional commands, e-mail: swansonlinda@example.org From swansonlinda@example.org Tue Jan 2 16:46:43 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 81589 invoked from network); 2 Jan 2001 16:46:43 -0000 Received: from notes.totalsystem.com (HELO internet?notes1.totalsystem.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 16:46:43 -0000 Received: from notes.dots.com ([83.161.120.155]) by mk-notesmail1.totalsystem.net (Lotus Domino Release 5.0.3) with ESMTP id 2001010211471339:1899 ; Tue, 2 Jan 2001 11:47:13 -0500 Received: from dots1024 ([83.161.120.155]) by notes.dots.com (Lotus Domino Release 5.0.3) with SMTP id 2001010211444721:1835 ; Tue, 2 Jan 2001 11:44:47 -0500 From: "Scott Carter" <swansonlinda@example.org> To: <swansonlinda@example.org> Subject: RE: Validation with SAX Date: Tue, 2 Jan 2001 11:55:10 -0500 Message-ID: <swansonlinda@example.org> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <swansonlinda@example.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal X-MIMETrack: Itemize by SMTP Server on notes/Dotsconnect(Release 5.0.3 |March 21, 2000) at 01/02/2001 11:44:47 AM, Serialize by Router on notes/Dotsconnect(Release 5.0.3 |March 21, 2000) at 01/02/2001 11:44:47 AM, Serialize complete at 01/02/2001 11:44:47 AM, Itemize by SMTP Server on MK-NOTESMAIL1/TotalSystem(Release 5.0.3 |March 21, 2000) at 01/02/2001 11:47:13 AM, Serialize by Router on Internet_Notes1/TSYSInternet(Release 5.0.3 |March 21, 2000) at 01/02/2001 11:41:56 AM, Serialize complete at 01/02/2001 11:41:56 AM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Thanks!! -----Original Message----- From: swansonlinda@example.org [mailto:swansonlinda@example.org] Sent: Tuesday, January 02, 2001 11:38 AM To: swansonlinda@example.org Subject: Re: Validation with SAX Hi Scott, Looks like you've got one of the more popular errors in these parts: you haven't declared an ErrorHandler. So you need to write a class implementing ErrorHandler to handle exceptions thrown by the SAX Parser and register it using the setErrorHandler method; i.e., append saxParser.setErrorHandler(handler); to this code snippet. You can look at the ErrorHandler.java interface in the org.xml.sax package. Hope that helps, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 2209615571, T/L 778-3519 E-mail: swansonlinda@example.org "Scott Carter" <swansonlinda@example.org> on 01/02/2001 11:18:37 AM Please respond to swansonlinda@example.org To: <swansonlinda@example.org> cc: Subject: Validation with SAX I have a simple question that I hope someone can answer. I'm trying to do a validating parse of a series of documents using SAX, but the problem I'm having is that the parser doesn't appear to be validating. I'm using JAXP to call the parser and I'm setting the validate option as follows: RequestHandler handler = new RequestHandler(); SAXParser saxParser = factory.newSAXParser(); factory.setValidating(true); saxParser.parse(docStream, handler); Any ideas why this is happening? --------------------------------------------------------------------- To unsubscribe, e-mail: swansonlinda@example.org For additional commands, e-mail: swansonlinda@example.org --------------------------------------------------------------------- To unsubscribe, e-mail: swansonlinda@example.org For additional commands, e-mail: swansonlinda@example.org From swansonlinda@example.org Tue Jan 2 17:42:57 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 33483 invoked from network); 2 Jan 2001 17:42:57 -0000 Received: from unknown (HELO nsmail.west.quiq.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 17:42:57 -0000 Received: from quiq.com ([83.161.120.155]) by nsmail.west.quiq.com (Netscape Messaging Server 4.15) with ESMTP id G6JMZT00.M1R for <swansonlinda@example.org>; Tue, 2 Jan 2001 08:26:17 -0800 Sender: "Luke Blanshard" <swansonlinda@example.org> Message-ID: <swansonlinda@example.org> Date: Tue, 02 Jan 2001 08:26:17 -0800 From: Luke Blanshard <swansonlinda@example.org> Organization: Quiq, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.13-0.7 i686) X-Accept-Language: en MIME-Version: 1.0 To: swansonlinda@example.org Subject: Re: Validation with SAX References: <swansonlinda@example.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Well, I have no idea what the JAXP interface looks like, but I can't believe you can call setValidating AFTER you create the parser and still expect the parser to validate! Luke Scott Carter wrote: > I have a simple question that I hope someone can answer. I'm trying to do a > validating parse of a series of documents using SAX, but the problem I'm > having is that the parser doesn't appear to be validating. I'm using JAXP > to call the parser and I'm setting the validate option as follows: > > RequestHandler handler = new RequestHandler(); > SAXParser saxParser = factory.newSAXParser(); > factory.setValidating(true); > saxParser.parse(docStream, handler); > > Any ideas why this is happening? From swansonlinda@example.org Tue Jan 2 18:50:22 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 14269 invoked from network); 2 Jan 2001 18:50:22 -0000 Received: from e31.co.us.ibm.com (HELO e31.bld.us.ibm.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 18:50:22 -0000 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [83.161.120.155]) by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id NAA17932 for <swansonlinda@example.org>; Tue, 2 Jan 2001 13:43:52 -0500 From: swansonlinda@example.org Received: from d25ml04.torolab.ibm.com (d25ml04.torolab.ibm.com [83.161.120.155]) by westrelay02.boulder.ibm.com (8.11.0m3/NCO v4.95) with ESMTP id f02IoL0151116 for <swansonlinda@example.org>; Tue, 2 Jan 2001 11:50:21 -0700 Importance: Normal Subject: Re: Parsing XML: How do I get the URL of the DTD?? To: swansonlinda@example.org X-Mailer: Lotus Notes Release 5.0.4a July 24, 2000 Message-ID: <swansonlinda@example.org> Date: Tue, 2 Jan 2001 13:50:18 -0500 X-MIMETrack: Serialize by Router on D25ML04/25/M/IBM(Release 5.0.4a |July 24, 2000) at 01/02/2001 01:50:21 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hi, Even though you're using the DOM parser, you still have access to the setEntityResolver method from the SAX. If you implement your own org.xml.sax.EntityResolver and register it with the above-mentioned method, you'll have access to the systemId and be able to do whatever you need to with it. Hope that helps, Neil Neil Graham XML Parser Development IBM Toronto Lab Phone: 2209615571, T/L 778-3519 E-mail: swansonlinda@example.org swansonlinda@example.org on 12/29/2000 02:45:15 PM Please respond to swansonlinda@example.org To: swansonlinda@example.org cc: Subject: Parsing XML: How do I get the URL of the DTD?? I am using the DOM parser to parse XML: org.apache.xerces.parsers.DOMParser parser = new org.apache.xerces.parsers.DOMParser(); parser.parse(source); The XML has an external DTD in URL form: <?xml version="1.0"?> <!DOCTYPE FIXML SYSTEM "file:///d:/Documents/DTD/blah/blah.dtd" > How do I get at the URL string? I believe this is called the SystemID?? I have tried everything, including: parser.getLocator().getSystemId(); But parser.getLocater() returns null. Any ideas? --------------------------------------------------------------------- To unsubscribe, e-mail: swansonlinda@example.org For additional commands, e-mail: swansonlinda@example.org From swansonlinda@example.org Tue Jan 2 19:06:44 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 38646 invoked from network); 2 Jan 2001 19:06:44 -0000 Received: from mms.tumbleweed.com (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 19:06:44 -0000 Received: from 83.161.120.155 by mms.tumbleweed.com with SMTP (Tumbleweed MMS SMTP Relay (MMS v4.7)); Tue, 02 Jan 2001 11:17:38 -0800 X-Server-Uuid: 538e6a8c-0f42-11d4-9400-000102237308 Received: from iceberg ([83.161.120.155]) by hawaii.tumbleweed.com ( Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-67083U1500L100S0V35) with SMTP id AAA527 for <swansonlinda@example.org>; Tue, 2 Jan 2001 11:06:16 -0800 Message-ID: <swansonlinda@example.org> X-Sender: swansonlinda@example.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 02 Jan 2001 11:06:16 -0800 To: swansonlinda@example.org From: swansonlinda@example.org Subject: Getting element types as defined in schema MIME-Version: 1.0 X-WSS-ID: 164CF6D8131957-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hello all, Reading DOM/SAX api docs, I tried to get information about how I would be able to get the custom-defined type of a given element in the instance document. For example I parse an XML instance document where I encounter an element <foo>. Element <foo> has been given a complexType name of <footype> in the corresponding XML schema. However, is there any way to get such information through any API methods available ? Thanks, - Alex From swansonlinda@example.org Tue Jan 2 19:08:42 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 40443 invoked from network); 2 Jan 2001 19:08:42 -0000 Received: from notes.totalsystem.com (HELO internet?notes1.totalsystem.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 19:08:42 -0000 Received: from notes.dots.com ([83.161.120.155]) by mk-notesmail1.totalsystem.net (Lotus Domino Release 5.0.3) with ESMTP id 2001010214080457:16 ; Tue, 2 Jan 2001 14:08:04 -0500 Received: from dots1024 ([83.161.120.155]) by notes.dots.com (Lotus Domino Release 5.0.3) with SMTP id 2001010214063685:1850 ; Tue, 2 Jan 2001 14:06:36 -0500 From: "Scott Carter" <swansonlinda@example.org> To: <swansonlinda@example.org> Subject: RE: Validation with SAX Date: Tue, 2 Jan 2001 14:17:00 -0500 Message-ID: <swansonlinda@example.org> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <swansonlinda@example.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal X-MIMETrack: Itemize by SMTP Server on notes/Dotsconnect(Release 5.0.3 |March 21, 2000) at 01/02/2001 02:06:36 PM, Serialize by Router on notes/Dotsconnect(Release 5.0.3 |March 21, 2000) at 01/02/2001 02:06:37 PM, Serialize complete at 01/02/2001 02:06:37 PM, Itemize by SMTP Server on MK-NOTESMAIL1/TotalSystem(Release 5.0.3 |March 21, 2000) at 01/02/2001 02:08:04 PM, Serialize by Router on Internet_Notes1/TSYSInternet(Release 5.0.3 |March 21, 2000) at 01/02/2001 02:03:57 PM, Serialize complete at 01/02/2001 02:03:57 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Actually, it was validating properly, I was not properly handling the resulting errors. Under SAX, since it is event based, errors that are not handled and specifically thrown, using the HandlerBase.error() method are ignored rather than being thrown back thanks for your help. Scott -----Original Message----- From: Luke Blanshard [mailto:swansonlinda@example.org] Sent: Tuesday, January 02, 2001 11:26 AM To: swansonlinda@example.org Subject: Re: Validation with SAX Well, I have no idea what the JAXP interface looks like, but I can't believe you can call setValidating AFTER you create the parser and still expect the parser to validate! Luke Scott Carter wrote: > I have a simple question that I hope someone can answer. I'm trying to do a > validating parse of a series of documents using SAX, but the problem I'm > having is that the parser doesn't appear to be validating. I'm using JAXP > to call the parser and I'm setting the validate option as follows: > > RequestHandler handler = new RequestHandler(); > SAXParser saxParser = factory.newSAXParser(); > factory.setValidating(true); > saxParser.parse(docStream, handler); > > Any ideas why this is happening? --------------------------------------------------------------------- To unsubscribe, e-mail: swansonlinda@example.org For additional commands, e-mail: swansonlinda@example.org From swansonlinda@example.org Tue Jan 2 19:31:33 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 60086 invoked from network); 2 Jan 2001 19:31:33 -0000 Received: from willy.pdq.net (HELO willy.taxrefund.com) (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 19:31:33 -0000 Received: from wobbet ([83.161.120.155]) by willy.taxrefund.com (8.9.3/8.9.3) with SMTP id NAA06534 for <swansonlinda@example.org>; Tue, 2 Jan 2001 13:35:34 -0600 From: "rsanford" <swansonlinda@example.org> To: <swansonlinda@example.org> Subject: RE: [Xerces2] Survey Date: Tue, 2 Jan 2001 13:31:30 -0600 Message-ID: <swansonlinda@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 In-Reply-To: <swansonlinda@example.org> X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > Well, the holidays have slowed everything down so I think that > now is a good time to take a survey from the Xerces community > about Xerces2. So, if you have the time, please respond to this > message with your responses. > > XERCES2 SURVEY > > Section 1: Usage > > 1) What parser are you using in your application? Select one > parser by putting an 'X' in the box next to your choice. If > you have a hybrid application that uses more than one parser, > select the most important parser for your application. > > [X] Xerces 1.x > [ ] Xerces 1.x packaged with Xalan > [ ] Xerces 2.x > [ ] XML4J 1.x/2.x > [ ] Crimson > [ ] _________________________ > > 2) If you did NOT select Xerces in question 1, what were your > reasons for not using Xerces in your application? Select all > that apply. > > [ ] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [ ] Specialized API (What features?) > [ ] License > [ ] _________________________ > > 3) If you DID select Xerces in question 1, what were your > reasons for using Xerces in your application? Select all > that apply. > > [X] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [ ] Specialized API (What features?) > [X] License > [X] both c++ & java w/ same api, ***recommended by peers*** > > Section 2: Xerces2 > > 4) What is your level of knowledge of Xerces2? Select all > that apply. > > [X] Followed the Xerces2 discussion on the mailing list > [X] Read the online documentation located at > http://www.apache.org/~andyc/xerces2/ > [ ] Reviewed the Xerces Native Interface (XNI) > [ ] Downloaded Xerces 2.0.0 (alpha) or extracted and built > the source from CVS > [ ] Tried Xerces2 in an application > > 5) If you have heard of Xerces2 but have NOT tried it, what > would you say is the primary reason? Select only one answer. > > [ ] Current parser works fine > [X] No time to try > [ ] _________________________ > > 6) Despite your current use of Xerces1, do you plan on moving > your application to using Xerces2 when a production version > becomes available? Select only one answer. > > [X] Yes > [ ] Wait and see > [ ] No > > 7) If you have reviewed XNI, what is your impression? Select > only one answer. > > [ ] Love it > [ ] Like it > [ ] Could be better > [ ] Hate it > [ ] Don't care > > 8) If you answered "Could be better" or "Hate it" to question > 6, what suggestions do you have? Please site specific > interfaces, methods, etc. > > 9) Do you plan on contributing to Xerces2? In what way? > > [ ] Yes > [ ] Source > [ ] Samples > [ ] Documentation > [ ] Build/Testing > [X] No > > Section 3: Wish List > > 10) What are the features that you would like to see implemented > in Xerces2? Rank the three most important to you by putting > a '1', '2', and '3' in the boxes next to your choices, where > '1' is the most important and '3' is the least important > among your choices. > > [ ] Grammar access > [1] Grammar caching > [3] Write validation: the ability to apply a grammar to > a document after parsing. For example, validate a DOM > tree after editing > [2] i don't really have a #2 > [ ] _________________________ > [ ] _________________________ From swansonlinda@example.org Tue Jan 2 19:42:07 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 67741 invoked from network); 2 Jan 2001 19:42:07 -0000 Received: from emerald.alltel.com (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 19:42:07 -0000 Received: from sbridge.lit.alltel.com ([83.161.120.155]) by emerald.alltel.com with MailMarshal (3,3,0,0) id <B000d7d21>; Tue, 02 Jan 2001 13:43:04 -600 Date: Tue, 02 Jan 2001 13:33 -0600 From: "Harris Hopper" <swansonlinda@example.org> To: "swansonlinda@example.org" <swansonlinda@example.org> Subject: RE: [Xerces2] Survey Message-ID: <swansonlinda@example.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N -----Original Message----- From: swansonlinda@example.org Sent: Thursday, December 28, 2000 11:46 PM To: Harris Hopper; swansonlinda@example.org Subject: [Xerces2] Survey Well, the holidays have slowed everything down so I think that now is a good time to take a survey from the Xerces community about Xerces2. So, if you have the time, please respond to this message with your responses. XERCES2 SURVEY Section 1: Usage 1) What parser are you using in your application? Select one parser by putting an 'X' in the box next to your choice. If you have a hybrid application that uses more than one parser, select the most important parser for your application. [x] Xerces 1.x [ ] Xerces 1.x packaged with Xalan [ ] Xerces 2.x [ ] XML4J 1.x/2.x [ ] Crimson [ ] _________________________ 2) If you did NOT select Xerces in question 1, what were your reasons for not using Xerces in your application? Select all that apply. [ ] Standards compliance [ ] Performance: speed [ ] Performance: memory usage [ ] Size of parser [ ] Specialized API (What features?) [ ] License [ ] _________________________ 3) If you DID select Xerces in question 1, what were your reasons for using Xerces in your application? Select all that apply. [x] Standards compliance [ ] Performance: speed [ ] Performance: memory usage [ ] Size of parser [ ] Specialized API (What features?) [x] License [ ] _________________________ Section 2: Xerces2 4) What is your level of knowledge of Xerces2? Select all that apply. [x] Followed the Xerces2 discussion on the mailing list [x] Read the online documentation located at http://www.apache.org/~andyc/xerces2/ [ ] Reviewed the Xerces Native Interface (XNI) [ ] Downloaded Xerces 2.0.0 (alpha) or extracted and built the source from CVS [ ] Tried Xerces2 in an application 5) If you have heard of Xerces2 but have NOT tried it, what would you say is the primary reason? Select only one answer. [ ] Current parser works fine [ ] No time to try [x] Waiting for schema support, reports of improved performance (speed) 6) Despite your current use of Xerces2, do you plan on moving your application to using Xerces2 when a production version becomes available? Select only one answer. [x] Yes [ ] Wait and see [ ] No 7) If you have reviewed XNI, what is your impression? Select only one answer. [ ] Love it [ ] Like it [ ] Could be better [ ] Hate it [ ] Don't care 8) If you answered "Could be better" or "Hate it" to question 6, what suggestions do you have? Please site specific interfaces, methods, etc. 9) Do you plan on contributing to Xerces2? In what way? [x] Yes [ ] Source [ ] Samples [ ] Documentation [x] Build/Testing [ ] No Section 3: Wish List 10) What are the features that you would like to see implemented in Xerces2? Rank the three most important to you by putting a '1', '2', and '3' in the boxes next to your choices, where '1' is the most important and '3' is the least important among your choices. [ ] Grammar access [1] Grammar caching [ ] Write validation: the ability to apply a grammar to a document after parsing. For example, validate a DOM tree after editing [2] Faster parse times [ ] _________________________ [ ] _________________________ -- Andy Clark * IBM, TRL - Japan * swansonlinda@example.org --------------------------------------------------------------------- To unsubscribe, e-mail: swansonlinda@example.org For additional commands, e-mail: swansonlinda@example.org From swansonlinda@example.org Tue Jan 2 19:52:55 2001 Return-Path: <swansonlinda@example.org> Mailing-List: contact swansonlinda@example.org; run by ezmlm Delivered-To: mailing list swansonlinda@example.org Received: (qmail 82216 invoked from network); 2 Jan 2001 19:52:55 -0000 Received: from mail.orbitcommerce.com (83.161.120.155) by h31.sny.collab.net with SMTP; 2 Jan 2001 19:52:55 -0000 Received: from pluto.chicago.orbitcommerce.com (pluto.chicago.orbitcommerce.com [83.161.120.155]) by mail.orbitcommerce.com (8.9.3/8.9.3) with ESMTP id NAA19090 for <swansonlinda@example.org>; Tue, 2 Jan 2001 13:52:30 -0600 (CST) Received: by pluto.chicago.orbitcommerce.com with Internet Mail Service (5.5.2650.21) id <ZNMK5Y6C>; Tue, 2 Jan 2001 13:51:40 -0600 Message-ID: <swansonlinda@example.org> From: Tung Mansfield <swansonlinda@example.org> To: "'swansonlinda@example.org'" <swansonlinda@example.org> Subject: RE: [Xerces2] Survey Date: Tue, 2 Jan 2001 13:51:32 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N -----Original Message----- From: rsanford [mailto:swansonlinda@example.org] Sent: Tuesday, January 02, 2001 1:32 PM To: swansonlinda@example.org Subject: RE: [Xerces2] Survey > Well, the holidays have slowed everything down so I think that > now is a good time to take a survey from the Xerces community > about Xerces2. So, if you have the time, please respond to this > message with your responses. > > XERCES2 SURVEY > > Section 1: Usage > > 1) What parser are you using in your application? Select one > parser by putting an 'X' in the box next to your choice. If > you have a hybrid application that uses more than one parser, > select the most important parser for your application. > > [X] Xerces 1.x > [ ] Xerces 1.x packaged with Xalan > [ ] Xerces 2.x > [ ] XML4J 1.x/2.x > [ ] Crimson > [ ] _________________________ > > 2) If you did NOT select Xerces in question 1, what were your > reasons for not using Xerces in your application? Select all > that apply. > > [ ] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [ ] Specialized API (What features?) > [ ] License > [ ] _________________________ > > 3) If you DID select Xerces in question 1, what were your > reasons for using Xerces in your application? Select all > that apply. > > [X] Standards compliance > [ ] Performance: speed > [ ] Performance: memory usage > [ ] Size of parser > [ ] Specialized API (What features?) > [X] License > [ ] both c++ & java w/ same api, ***recommended by peers*** > > Section 2: Xerces2 > > 4) What is your level of knowledge of Xerces2? Select all > that apply. > > [ ] Followed the Xerces2 discussion on the mailing list > [ ] Read the online documentation located at > http://www.apache.org/~andyc/xerces2/ > [ ] Reviewed the Xerces Native Interface (XNI) > [ ] Downloaded Xerces 2.0.0 (alpha) or extracted and built > the source from CVS > [ ] Tried Xerces2 in an application > > 5) If you have heard of Xerces2 but have NOT tried it, what > would you say is the primary reason? Select only one answer. > > [ ] Current parser works fine > [ ] No time to try > [X] What do I gain by going to Xerces2?_________________________ > > 6) Despite your current use of Xerces1, do you plan on moving > your application to using Xerces2 when a production version >
{'source': 'Apache Software Foundation Public Mail Archives'}