my dog learned polymorphism*
The moose likes Tomcat and the fly likes Different XML validation behavior on Tomcat 4.1 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Different XML validation behavior on Tomcat 4.1" Watch "Different XML validation behavior on Tomcat 4.1" New topic
Author

Different XML validation behavior on Tomcat 4.1

Jason Liao
Ranch Hand

Joined: Jun 17, 2005
Posts: 59
Hi, All,

I use Xerces-J to validate XML and it works fine in dev server, but it does bypass the validation in other servers (same windows OS), even the same code and configurations. Did you meet the same situation before?

Thanks in advance.

Jason


My environment: XercesJ 2.6.2 + Tomcat 4.1.27 + JDK 1.3.1+ windows 2000 server.

My code: use DOMParser.

Expeceted validation messages:

[org.xml.sax.SAXParseException: cvc-maxLength-valid: Value '12345678901' with length = '11' is not facet-valid with respect to maxLength '9'., org.xml.sax.SAXParseException: cvc-type.3.1.3: The value '12345678901' of element 'CODE' is not valid.]
Jason Liao
Ranch Hand

Joined: Jun 17, 2005
Posts: 59
Just figure it out. XML namespaces are different in other servers.

Thanks for review.

Jason
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Different XML validation behavior on Tomcat 4.1