Yes. your solution is correct. Thank you very much!
"Barat, Arup" wrote:
If you used XML Spy 3.5 or earlier to write your
schema make sure that it
uses the may 2001 recommendation:
http://www.w3.org/2001/XMLSchema"
>
and not
http://www.w3.org/2000/10/XMLSchema"
> which is the
default. That shoul
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2169
*** shadow/2169 Wed Jun 13 18:28:32 2001
--- shadow/2169.tmp.21490 Mon Jun 18 16:29:09 2001
***
*** 2,9
| bug in org.apache.xerces.dom.DeferredAttrNSImpl|
+---
Title: Unsubscribe problems
Hello all,
I have followed the following instructions:
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2054
*** shadow/2054 Thu Jun 7 08:07:24 2001
--- shadow/2054.tmp.20789 Mon Jun 18 12:24:54 2001
***
*** 2,9
| Methods getType() from class org.xml.sax.Attributes produce incorrect outp |
+---
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2059
*** shadow/2059 Thu Jun 7 13:45:24 2001
--- shadow/2059.tmp.20775 Mon Jun 18 12:24:22 2001
***
*** 2,9
| SAX2-EXT-1.0: or does not trigger the attribute |
+
If you used XML Spy 3.5 or earlier to write your schema make sure that it
uses the may 2001 recommendation:
http://www.w3.org/2001/XMLSchema"; >
and not
http://www.w3.org/2000/10/XMLSchema"; > which is the
default. That should solve your problem.
cheers,
Arup Barat
-Original Message-
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=709
*** shadow/709 Fri Jun 8 06:39:14 2001
--- shadow/709.tmp.20288Mon Jun 18 11:31:04 2001
***
*** 2,9
| Cannot parse XML of exactly 16Kb in size (perhaps multiples thereof) |
+
Hi Willy,
If you set everything correctly, and the parser still gives you some
errors, then 99% there is an error in your xml file. :-)
It would definitely help if you could post your xml & xsd files, and it's
more reasonable to send such kind of questions to the user list
([EMAIL PROTECTED]).
>
> Hey all,
>
> I am seeing a problem using the encode and decode routines of
> xerces (1.3.1)
> to encode and decode binary data. After encoding a file of
> exactly 1674
> bytes I then decode it and find the file size is 1676 bytes.
> After looking
> at the source the problem appears to b
Hi Jeff,
I suggest that you get the latest version of Base64.java from CVS (xerces
1.4.0 should be ok too, but I didn't confirm). Some bugs in decode method
have been fixed.
If you still have problem with it, feel free to let me know.
Thanks,
Sandy Gao
Software Developer, IBM Canada
(1-416) 448
[EMAIL PROTECTED] wrote:
>
> Hi all,
>
> In many classes, to detect the need of array-resizing, we try to access a
> specific position, and do the resizing when
> "ArrayIndexOutOfBoundsException" is caught (or NullPointerException for
> multidimensional arrays).
>
> But my understanding is that
Hello all,
I just like my xml file to be validated against the schema, I create
the schema
using XML Spy, so I use the ff code:
parser.setFeature( "http://xml.org/sax/features/validation",true);
parser.setFeature( "http://xml.org/sax/features/namespaces",true );
parser.setFeature(
"http://apac
Hey all,
I am seeing a problem using the encode and decode routines of xerces (1.3.1)
to encode and decode binary data. After encoding a file of exactly 1674
bytes I then decode it and find the file size is 1676 bytes. After looking
at the source the problem appears to be in the padding. The e
i want to parse an xml document against the xml schema ,but it only
checks for well formedness and not validation of document.i am using an
xerces-j parser for the same and parsing in a servlet hosted on an apache
web server.
for this i have set the required features and error handler but stil
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2218
*** shadow/2218 Mon Jun 18 10:40:01 2001
--- shadow/2218.tmp.20107 Mon Jun 18 10:40:01 2001
***
*** 0
--- 1,1039
+ ++
+ | NULL Pointer exc
Hi all. I'm trying to fix this bug, but I need some clarification on
attributes from other namespaces.
The following segment is from "schema for schemas":
This type is extended by almost all schema types
to allow attributes from other namespaces to be
added to us
Hi Klaus,
Thanks for your patch. I've checked it in.
Cheers,
Sandy Gao
Software Developer, IBM Canada
(1-416) 448-3255
[EMAIL PROTECTED]
"Kiehne, Z 198,
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1070
*** shadow/1070 Sun May 20 17:23:44 2001
--- shadow/1070.tmp.19647 Mon Jun 18 09:08:53 2001
***
*** 1,18
! Bug#: 1070
! Product: Xerces-J
! Version: 1.3.0
! Platform: PC
! OS/Version: All
! Status: NEW
! Resolution:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2216
*** shadow/2216 Mon Jun 18 09:04:09 2001
--- shadow/2216.tmp.19613 Mon Jun 18 09:04:57 2001
***
*** 2,13
| Namespaces for attributes of schema elements not processed |
+--
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2216
*** shadow/2216 Mon Jun 18 08:57:22 2001
--- shadow/2216.tmp.19601 Mon Jun 18 09:04:09 2001
***
*** 2,8
| Namespaces for attributes of schema elements not processed |
+---
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2216
*** shadow/2216 Mon Jun 18 08:57:22 2001
--- shadow/2216.tmp.19557 Mon Jun 18 08:57:22 2001
***
*** 0
--- 1,38
+ ++
+ | Namespaces for att
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2194
*** shadow/2194 Fri Jun 15 10:06:37 2001
--- shadow/2194.tmp.19464 Mon Jun 18 08:19:53 2001
***
*** 35,37
--- 35,45
would actually be a deficiency if they DIDN'T buffer the data. IMHO, the
current implementat
Hi,
I've found a bug in Xerces (v 1.3.1) using schema validation and two schemas.
This bug exists also in V1.4.0 and seems still to exist in the most recent
version of the code in the CVS repository.
Bug description by example :
I've got two schemas the first schema holds type definitions, the
> or call
> "putIdentifier" explicitly, otherwise how would the parser know whether
> this newly added attribute has type "ID"?
Please, note, the above solution [suggested by Evert/Sandy] is a hack
into Xerces implementation. If you use it, you code is no longer
COMPLIANT with DOM Rec (it will onl
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2213
*** shadow/2213 Mon Jun 18 07:15:14 2001
--- shadow/2213.tmp.19314 Mon Jun 18 07:16:58 2001
***
*** 17,19
--- 17,23
Parameter entities in DTD ATTLIST markup are reported as overlayed with
startAttlist() callbac
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2213
*** shadow/2213 Mon Jun 18 07:15:14 2001
--- shadow/2213.tmp.19298 Mon Jun 18 07:15:14 2001
***
*** 0
--- 1,19
+ ++
+ | Callback order PAT
Hi Kusuma,
> Is this a bug ?why doesn't xerces automatically call putIdentifier?
You have to either define such attributes in DTD/Schema, or call
"putIdentifier" explicitly, otherwise how would the parser know whether
this newly added attribute has type "ID"?
The name "id" is not sufficient. No
Thanx..i was not knowing this. I was breaking brains why the newly created
nodes are not being recognized. Is this a bug ?why doesn't xerces
automatically call putIdentifier? I have a major problem. My application
needs two xml nodes to be swapped. Once i swap the node it's not being
recognized by
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2210
*** shadow/2210 Mon Jun 18 03:40:04 2001
--- shadow/2210.tmp.18773 Mon Jun 18 03:40:04 2001
***
*** 0
--- 1,19
+ ++
+ | Parser does not su
Hi
I am working on some code to capture the invalid nodes from a document. The
SAXParseException thrown only allows me to gain information on the line
number, column name and the error message.
In order to capture the node I was thinking about using the setProperty
method
setProperty("http://ap
30 matches
Mail list logo
