You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Bernhard Dorninger <be...@scch.at> on 2000/08/30 18:07:46 UTC

Xerces 1.1.3 SAX2 namespace bug?

I am sorry, if this has already been an issue...
if(topic.wasHandled())
	this.ignore();


I am parsing the following SOAP message with
"org.apache.xerces.parsers.SAXParser" (Xerces 1.1.3):
-----
<SOAP-ENV:Envelope
	xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
	SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
  <SOAP-ENV:Header>
    <myns:Entry xmlns:myns="urn:java:at.scch.soap"
SOAP-ENV:mustUnderstand="1">c354322
    </myns:Entry>
  </SOAP-ENV:Header>
  <SOAP-ENV:Body>
	<Foo/>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
---------

Now the problem is that at the start of "Header", the SAX2 method
"startElement" delivers the right URI., but "endElement" for "Header"
delivers the URI defined for "Entry" ????

----Output from modified SAX2Count:

END-ELEMENT:
uri=urn:java:at.scch.soap
local=Entry
raw(qname)=myns:Entry
CDATA(1 chars):


END-ELEMENT:
uri=urn:java:at.scch.soap
local=Header
raw(qname)=SOAP-ENV:Header
CDATA(1 chars):
--------

The following "Body" Element's "startElement" call shows the right
"SOAP-ENV"-URI again.
Is this deliverance of a wrong ns-uri a bug or do i have to track ns-decls
on my own, e.g with the NamespaceSupport class?

Thx for help
Bernhard

------------------
Bernhard Dorninger

Software Competence Center Hagenberg GmbH
Softwarepark Hagenberg, Hauptstraße 99
A-4232 Hagenberg, Austria
Tel.: +43 7236 3343 891
Fax: +43 7236 3343 888
mailto:bernhard.dorninger@scch.at
http://www.scch.at