Hi David,

Is there anything like this in your xsd file (mixed-empty complexType)?

<complexType mixed="true">
   <attribute .../>
</complexType>

If so, it's a bug in 1.4.1, and it should have been fixed in CVS. Grab the
latest copy and try again. Hopefully it would work. If still not, sending
the xml/xsd files would help us looking at the problem.

Cheers,
Sandy Gao
Software Developer, IBM Canada
(1-416) 448-3255
[EMAIL PROTECTED]



                                                                                
                                   
                    "NeSmith,                                                   
                                   
                    David"               To:     "'[EMAIL PROTECTED]'" <[EMAIL 
PROTECTED]>   
                    <[EMAIL PROTECTED]       cc:                                
                                       
                    ra.com>              Subject:     RE: Schema validation 
problems                               
                                                                                
                                   
                    07/05/2001                                                  
                                   
                    06:36 PM                                                    
                                   
                    Please respond                                              
                                   
                    to                                                          
                                   
                    xerces-j-user                                               
                                   
                                                                                
                                   
                                                                                
                                   



when I ran the xercesSamples sax.SAXCount example on my xml file I have the
same result however the stack trace showed a bit more info....

java.lang.NullPointerException
        at
org.apache.xerces.validators.common.XMLValidator.checkContent(XMLVali
dator.java:4136)
        at
org.apache.xerces.validators.common.XMLValidator.callEndElement(XMLVa
lidator.java:1386)
        at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.disp
atch(XMLDocumentScanner.java:1260)
        at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentS
canner.java:381)
        at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1081)
        at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1122)
        at sax.SAXCount.print(SAXCount.java:158)
        at sax.SAXCount.main(SAXCount.java:392)

PS: I just saw your email J�rn and my xml file and schema are in the same
location...

-----Original Message-----
From: NeSmith, David [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 05, 2001 6:01 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Schema validation problems


PS: I am using jdk1.3 and Xerces 1.4.1

-----Original Message-----
From: NeSmith, David [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 05, 2001 5:56 PM
To: '[EMAIL PROTECTED]'
Subject: Schema validation problems


I am getting a null pointer exception every time I try to validate a file
against it's schema. It says what validation errors are in the file or it
says nothing if there is no validation error.  But directly after that
there
is a null pointer.  These are the features I turned on.

parser.setFeature("http://xml.org/sax/features/validation";, true);
parser.setFeature("http://apache.org/xml/features/validation/schema";,
true);
parser.setFeature("
http://apache.org/xml/features/validation/schema-full-che
cking", true);
parser.setFeature("http://apache.org/xml/features/dom/defer-node-expansion
",
true);

java.lang.NullPointerException            at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1094)

any help?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to