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.
Commented: (XERCESJ-1165) Problem resolving namespace prefix for QName, s

Commented: (XERCESJ-1165) Problem resolving namespace prefix for QName, s

2006-05-18       - By Michael Glavassevich (JIRA)
Reply:     1     2     3  

   [ http://issues.apache.org/jira/browse/XERCESJ-1165?page=comments#action
_12412364 ]

Michael Glavassevich commented on XERCESJ-1165:
-----------------------------------------------

The object reference comparison is by design and not a bug.  If you look around
the Xerces codebase, you'll see these everywhere instead of String.equals(). It
's done for performance reasons and works because the String objects are unique
(see org.apache.xerces.util.SymbolTable).

Which API in JAXP did you use for schema validation? Are you sure you were
actually using Xerces 2.8.0 and not the validator embedded in Java 1.5.0?

> Problem resolving namespace prefix for QName, suspected bug in
NamespaceSupport
> -----------------------------------------------------------------------------
--
>
>          Key: XERCESJ-1165
>          URL: http://issues.apache.org/jira/browse/XERCESJ-1165
>      Project: Xerces2-J
>         Type: Bug

>   Components: XML Schema API
>     Versions: 2.8.0
>  Environment: Windows XP SP2, JRE 1.5.0_06
>     Reporter: Jonathan Mezach

>
> I think I found a bug in the NamespaceSupport class which is part of Xerces2
-J. I'm working on a project which involves elements which have a QName as type.
Let me just write some XML to clarify:
> <xbrli:xbrl xmlns:iso4217="http://www.xbrl.org/2003/iso4217">
>  <xbrli:unit id="EUR">
>   <xbrli:measure>iso4217:EUR</xbrli:measure>
>  </xbrli:unit>
> </xbrli:xbrl>
> I'm trying to validate this using JAXP with the Xerces implementation. The
schema for the measure element is as follows:
> <xsd:element name="measure" type="QName"/>
> Now, when the validation is run an exception is thrown which reads as follows:
> UndeclaredPrefix: Cannot resolve 'iso4217:EUR' as a QName: the prefix
'iso4217' is not declared.
> This is quite strange because the namespace prefix is clearly declared at the
top level element. So I decided to have a debug through the code and found that
the problem is in the NamespaceSupport class. At the bottom of the
getActualValue method of the QNameDV class the method getURI is called on the
ValidationContext that was passed to it. This eventually calls the getURI
(String) method on the NamespaceSupport class. The code here reads as follows:
> 1.       // find prefix in current context
> 2.        for (int i = fNamespaceSize; i > 0; i -= 2) {
> 3.            if (fNamespace[i - 2] == prefix) {
> 4.                return fNamespace[i - 1];
> 5.            }
> 6.        }
> 7.
> 8.        // prefix not found
> 9.        return null;
> The fNamespace instance variable is a String array and the prefix argument is
a String as well. This leads me to conclude that line 3 of the above code
should have been written as follows:
> if (fNamespace[i -2].equals(prefix)) {
> String comparison in Java is done using the equals method rather than the
equals operator as far as I know.

--
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
-
For more information on JIRA, see:
  http://www.atlassian.com/software/jira


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