Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Resolved: (XERCESJ-979) default of the feature "http://xml.org/sax/featur

Resolved: (XERCESJ-979) default of the feature "http://xml.org/sax/featur

2004-06-11       - By jira@(protected)

Message:

  The following issue has been resolved as INCOMPLETE.

  Resolver: Michael Glavassevich
      Date: Fri, 11 Jun 2004 10:36 AM

The default depends on how've you created the parser. JAXP says the default is
false [1]. SAX says the default is true [2]. There isn't a bug here. It's just
a conflict between the two specs which often burns users who assume that SAX
and JAXP are consistent. Glancing at the source code for XMLValidateTask [3]
and JAXPUtils [4] a non-namespace aware JAXP SAXParser is being created and
used.

As to whether namespace support is required for schema processing and
validation, it's not specific to Xerces. W3C XML Schemas are built upon XML
namespaces (among other standards).

[1] http://java.sun.com/j2se/1.4.2/docs/api/javax/xml/parsers/SAXParserFactory
.html#setNamespaceAware(boolean)
[2] http://www.saxproject.org/apidoc/org/xml/sax/package-summary.html
[3] http://cvs.apache.org/viewcvs.cgi/ant/src/main/org/apache/tools/ant
/taskdefs/optional/XMLValidateTask.java?annotate=1.36.2.5
[4] http://cvs.apache.org/viewcvs.cgi/ant/src/main/org/apache/tools/ant/util
/JAXPUtils.java?annotate=1.9.2.5
---------------------------------------------------------------------
View the issue:
 http://issues.apache.org/jira/browse/XERCESJ-979

Here is an overview of the issue:
---------------------------------------------------------------------
       Key: XERCESJ-979
   Summary: default of the feature "http://xml.org/sax/features/namespaces"
      Type: Bug

    Status: Resolved
  Priority: Major
Resolution: INCOMPLETE

   Project: Xerces2-J
  Versions:
            2.6.2

  Assignee:
  Reporter: Antoine Levy-Lambert

   Created: Fri, 11 Jun 2004 6:22 AM
   Updated: Fri, 11 Jun 2004 10:36 AM
Environment: Windows 2000 German, cygwin, JDK 1.4, ant 1.6.1

Description:
I have been working on a bug report http://issues.apache.org/bugzilla/show_bug
.cgi?id=29187 titled "xmlvalidate schema validation not working".
I found out that if the following XML fragment is added to   <attribute name=
"http://xml.org/sax/features/namespaces" value="true"/> the body of the
xmlvalidate tag in the ant project file, then the validation works.

But the documentation of xerces says that the namespaces feature defaults to
true.

http://xml.apache.org/xerces-j/features.html

So I suspect one of 3 possibilities :

- documentation bug : the default of the feature is false,
- code bug : the intended default for this feature is true, but the code sets
it to false or "forgets" to set it explicitly to true
- something specific for the xml schema validation implementation present in
xerces ???

I will add the feature to one of the examples in the documentation of ant.

Cheers,
Antoine


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
  http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
  http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-dev-help@(protected)