[Bug 2010] - XMLSerializer is final

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2010 *** shadow/2010 Tue Jun 5 10:51:00 2001 --- shadow/2010.tmp.2171Mon Jun 11 13:10:12 2001 *** *** 2,9 | XMLSerializer is final | +---

RE: Bug with XMLDocumentScanner.java (fix provided) (xerces 1.4.0, 1.3.1, 1.3.0)

2001-06-11 Thread Glenn Marcy
Luke, WSDL documents cetainly must follow the specification. Whoever is creating them is producing ill-formed XML documents. Since the definition of a well-formed document is in part that it matches the productions in the grammar, the restriction comes from the following productions: [1] do

Dom TreeWalker

2001-06-11 Thread Ben Sifuentes
I have a XML & XSL definition that looks like so: XML --- line1 line1 line1 XSL --- http://www.w3.org/1999/XSL/Transform";> "); I want to manualy walk the dom tree and get each element of Now I thought I could use the TreeWalker class but when I look at this class I see a t

Dom TreeWalker

2001-06-11 Thread Ben Sifuentes
I have a XML & XSL definition that looks like so: XML --- line1 line1 line1 XSL --- http://www.w3.org/1999/XSL/Transform";> "); I want to manualy walk the dom tree and get each element of Now I thought I could use the TreeWalker class but when I look at this class I see a t

RE: Bug with XMLDocumentScanner.java (fix provided) (xerces 1.4.0, 1.3.1, 1.3.0)

2001-06-11 Thread Luke Chen
Glenn, I suspected that might be the case, but didn't find such assertion in the XML specs when I last tried, but did notice that the code was deliberatly strict. From a utilitarion view point, it would seem like a good idea to somehow be able to allow some flexibility in parsing, but at the

FW: Dom TreeWalker

2001-06-11 Thread Ben Sifuentes
-Original Message- From: Ben Sifuentes [mailto:[EMAIL PROTECTED]] Sent: Monday, June 11, 2001 11:18 AM To: Xerces-J-Dev Subject: Dom TreeWalker I have a XML & XSL definition that looks like so: XML --- line1 line1 line1 XSL --- http://www.w3.org/1999/XSL/Transform";> ");

[Bug 2115] - cos-element-consistent constraint not always applied

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2115 *** shadow/2115 Mon Jun 11 07:54:57 2001 --- shadow/2115.tmp.26381 Mon Jun 11 08:07:38 2001 *** *** 7,13 | Severity: Normal OS/Version: All | | Priority: Other

[Bug 2117] New: - DOMParser does not parse a processing instruction properly

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2117 *** shadow/2117 Mon Jun 11 08:06:15 2001 --- shadow/2117.tmp.26360 Mon Jun 11 08:06:15 2001 *** *** 0 --- 1,26 + ++ + | DOMParser does not

[Bug 2115] New: - cos-element-consistent constraint not always applied

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2115 *** shadow/2115 Mon Jun 11 07:54:56 2001 --- shadow/2115.tmp.26210 Mon Jun 11 07:54:57 2001 *** *** 0 --- 1,54 + ++ + | cos-element-consis

[Bug 1097] - #included XML Schema not found if Schemas & XML instance are in separate directories

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1097 *** shadow/1097 Sun May 20 17:23:53 2001 --- shadow/1097.tmp.25834 Mon Jun 11 06:38:36 2001 *** *** 1,19 ! Bug#: 1097 ! Product: Xerces-J ! Version: cvs extract (inc ! Platform: PC ! OS/Version: Windows NT/2K ! Status:

Re: [xerces2] Patch of external entity handling

2001-06-11 Thread Petr Kuzel
Petr Kuzel wrote: > > An attached patch fixes the behaviour by reporting a warning. > I have found in XMLEntityManager source another bug, so I created a bug report: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2110 and attached more complex patch of the XMLEntityManager to it. Cc.

[Bug 2110] - XMLEntityManager does not handle external entities well.

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2110 *** shadow/2110 Mon Jun 11 06:31:12 2001 --- shadow/2110.tmp.25791 Mon Jun 11 06:32:37 2001 *** *** 21,23 --- 21,27 2) It does not handle well nested external entities. All subsequent entities use as the baseSy

[Bug 2110] New: - XMLEntityManager does not handle external entities well.

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2110 *** shadow/2110 Mon Jun 11 06:31:12 2001 --- shadow/2110.tmp.25777 Mon Jun 11 06:31:12 2001 *** *** 0 --- 1,23 + ++ + | XMLEntityManager d

[Bug 2104] - URI may enter infinite loop

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2104 *** shadow/2104 Mon Jun 11 03:11:13 2001 --- shadow/2104.tmp.25718 Mon Jun 11 06:20:45 2001 *** *** 52,54 --- 52,59 --- Additional Comments From [EMAIL PROTECTED] 2001-06-11 03:11 --- Created an attach

unsubscribe me

2001-06-11 Thread Gus Delgado
unsubscribe me -Original Message- From: Glenn Marcy [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 09, 2001 9:28 AM To: [EMAIL PROTECTED] Subject: Re: Bug with XMLDocumentScanner.java (fix provided) (xerces 1.4.0, 1.3.1, 1.3.0) Luke, The XMLDecl, i.e. , if present in the document, i

[Bug 2104] - URI may enter infinite loop

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2104 *** shadow/2104 Mon Jun 11 03:08:01 2001 --- shadow/2104.tmp.25194 Mon Jun 11 03:11:13 2001 *** *** 48,50 --- 48,54 at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:195) at org.apa

[Bug 2104] New: - URI may enter infinite loop

2001-06-11 Thread bugzilla
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2104 *** shadow/2104 Mon Jun 11 03:08:01 2001 --- shadow/2104.tmp.25185 Mon Jun 11 03:08:01 2001 *** *** 0 --- 1,50 + ++ + | URI may enter infi