thought I'd answer my own question, correct some typos... xmlToString() should read "ElementToString()"
The problem arose because, in trying to build a more correct webapp, I put Oracle's XML parser in my WEB-INF/lib directory (it had been in Tomcat's lib directory before). It was responsible for the renegade "xmlns:=" and also caused other weirdness, like breaking the AdminClient. I guess Axis needs some other parser in the classpath before Oracle's XML parser. Are there known problems with Axis and Oracle's XML parser, or is there some simple explanation that I'd see if I knew more about Java, Axis, parsers, and classpaths? (like maybe something about Axis needing a JAXP-compliant parser and Oracle's parser messing things up if it's first in the classpath?) Andrew At 11:18 AM 6/17/2002 -0500, you wrote: >Hi all-- > >I have been using JSP to drive an Axis client to test my Axis messaging >service. It displays the body of the returned SOAP Envelope using the >XMLUtils.ElementToString() function. Has this function changed >post-beta2? I started a new webapp with a more recent Axis build (May >31), and the reason I notice the difference is that IE's default XSL >stylesheet can't handle the new results of ElementToString(). I am >returning SOAPBody contents with no namespace. ElementToString() used to >return something like this: > ><some_xml>blah</some_xml> > >and now returns something like this: > ><some_xml xmlns:="">blah</some_xml> > >The IE error I get is: > >"Only a default namespace can have an empty URI. Error processing resource" > >is xmlToString() doing the right thing? > >Andrew > >
