Looking into the Apache SOAP code, I suspect the DOM2Writer#serializeAsXml
method. If both the prefix and namespace URI for the DOM Element are
non-null, it will write the namespace information. As created in
buildFaultDetailsFromThrowable, does Xerces give the element null values for
these, or
ile:/J:/jakarta-tomcat-4.0-b6/bin/bootstrap.jar
> file:/J:/jdk1.3.0_01/lib/tools.jar
> file:/K:/Program Files/Allaire/JRun/lib/ext/mail.jar
> file:/K:/Program Files/Allaire/JRun/lib/ext/activation.jar
>
> Scott
>
> - Original Message -
> From: "David Turner"
r
> -
> -
> file:/J:/xerces-1_2_3/xerces.jar
> file:/J:/jakarta-tomcat-4.0-b6/bin/bootstrap.jar
> file:/J:/jdk1.3.0_01/lib/tools.jar
> file:/K:/Program Files/Allaire/JRun/lib/ext/mail.jar
> file:/K:/Program Files/Allaire/JRun/lib/ext/activation.jar
>
> Scott
>
:/Program Files/Allaire/JRun/lib/ext/activation.jar
Scott
- Original Message -
From: "David Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 31, 2001 3:19 PM
Subject: Re: Parsing error...
> An update:
> It looks like I was able to get the server
; Scott
>
> - Original Message -
> From: "David Turner" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, July 31, 2001 2:12 PM
> Subject: Re: Parsing error...
>
> > Hi Scott,
> >
> > My server classpath is as foll
then found
out what the "real" problem was after setting JAVA_COMPILER.
Scott
- Original Message -
From: "David Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 31, 2001 2:12 PM
Subject: Re: Parsing error...
> Hi Scott,
>
&g
t; Scott
>
> - Original Message -
> From: "David Turner" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, July 31, 2001 9:40 AM
> Subject: Re: Parsing error...
>
> > Hi Scott,
> >
> > I tried getting the classpath u
ar;%CATALINA_HOME%\bin\bootstrap.jar;%JAVA_HOME%\
> lib\tools.jar;k:\progra~1\allaire\jrun\lib\ext\mail.jar;k:\progra~1\allaire\
> jrun\lib\ext\activation.jar
>
> Scott
>
> - Original Message -
> From: "David Turner" <[EMAIL PROTECTED]>
> To: <[EMAI
Scott
- Original Message -
From: "David Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 31, 2001 9:40 AM
Subject: Re: Parsing error...
> Hi Scott,
>
> I tried getting the classpath used by the class loader via the code you
> recomme
avid Turner" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, July 31, 2001 9:40 AM
> Subject: Re: Parsing error...
>
>
> > Hi Scott,
> >
> > I tried getting the classpath used by the class loader via the code you
> > recommende
velopment, it requires overhead to do the
checking. This capability should generally not be used in deployed
production applications.
<<<<
Scott
- Original Message -
From: "David Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 31, 2001 9:4
TECTED]>
> Sent: Monday, July 30, 2001 4:18 PM
> Subject: Re: Parsing error...
>
> > In RPCRouterServlet I checked the class of the document builder being
> returned
> > by XMLParserUtils.getXMLDocBuilder() and it's as follows:
> > xdb documentBuilder class typ
But the weird thing about this is that there isn't any thing in the
JAVA_HOME\jre\lib\ext directory. That's why I'm puzzled on this one.
William Brogden wrote:
> David Turner wrote:
> >
> > In RPCRouterServlet I checked the class of the document builder being returned
> > by XMLParserUtils.ge
>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 30, 2001 4:18 PM
Subject: Re: Parsing error...
> In RPCRouterServlet I checked the class of the document builder being
returned
> by XMLParserUtils.getXMLDocBuilder() and it's as follows:
> xd
David Turner wrote:
>
> In RPCRouterServlet I checked the class of the document builder being returned
> by XMLParserUtils.getXMLDocBuilder() and it's as follows:
> xdb documentBuilder class type = class
> org.apache.crimson.jaxp.DocumentBuilderImpl
>
> I don't understand why the crimson v
: <[EMAIL PROTECTED]>
> Sent: Friday, July 27, 2001 11:30 AM
> Subject: Re: Parsing error...
>
> > Scott,
> > I dumped the System environment variables and I don't see anything
> unusual.
> >
> > Also, One thing I completely forgot to mention is that
way.
Scott
- Original Message -
From: "David Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 27, 2001 11:30 AM
Subject: Re: Parsing error...
> Scott,
> I dumped the System environment variables and I don't see anything
unusual.
http://www.w3.org/2000/xmlns/ is the namespace URI for xmlns.
Scott
- Original Message -
From: "David Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 27, 2001 12:08 PM
Subject: Re: Parsing error...
> Scott,
> The line in red (with
Scott,
I dumped the System environment variables and I don't see anything unusual.
Also, One thing I completely forgot to mention is that the version that I got
working (Linux and Win) I used JDK1.4.0beta. Here I'm using JDK1.3.0. That
shouldn't have anything to do with it, right?
java.runt
OTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 26, 2001 2:51 PM
Subject: Re: Parsing error...
> Further debug info:
> I stuck a couple of println's in the DOMUtils.getAttributeNS() method
just
prior to the line:
>
> Attr attr = el.getAttributeNodeNS(namespaceURI,
l
> Or a simpler thing to do at any point would be something like
>
> ClassLoader loader = Thread.currentThread().getContextClassLoader();
> if (loader instanceof URLClassLoader) {
> URL[] urls = loader.getURLs();
Make that
URL[] urls = ((URLClassLoader)loader).getURLs();
tln(urls[i]);
}
I'm not 100% certain this will work, but it seems worth a try just to see
what the classpath looks like.
Scott
- Original Message -
From: "David Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 26, 2001 2:51
et.
Scott
- Original Message -
From: "David Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 26, 2001 2:51 PM
Subject: Re: Parsing error...
> Further debug info:
> I stuck a couple of println's in the DOMUtils.getAttributeNS() metho
cott
>
> - Original Message -
> From: "David Turner" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, July 26, 2001 1:47 PM
> Subject: Re: Parsing error...
>
> > Scott,
> >
> > Here's a little more info on this is
> at java.lang.Thread.run(Thread.java:484)
>
> Scott Nichol wrote:
>
> > Sorry that I missed the fact your error was trying to deploy the services,
> > not run them. I'll try installing Tomcat 4 if I get the chance today or
> > tomorrow.
> >
&g
es instead, but since you said you ran
successfully on NT and Linux, that probably does not make sense.
Scott
- Original Message -
From: "David Turner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 26, 2001 1:47 PM
Subject: Re: Parsing error...
orry that I missed the fact your error was trying to deploy the services,
> not run them. I'll try installing Tomcat 4 if I get the chance today or
> tomorrow.
>
> Scott
>
> - Original Message -
> From: "David Turner" <[EMAIL PROTECTED]>
> To:
ursday, July 26, 2001 10:01 AM
Subject: Re: Parsing error...
> Hi Scott,
> I'm using tomcat 4.0 on a Tru64 machine. I can't run my stuff or the
samples
> because the problem I described occurs when deploying the services.
>
> Scott Nichol wrote:
>
> > You'
Hi Scott,
I'm using tomcat 4.0 on a Tru64 machine. I can't run my stuff or the samples
because the problem I described occurs when deploying the services.
Scott Nichol wrote:
> You've done some thorough investigating, but I am curious whether the
> samples work.
>
> What servlet container are y
You've done some thorough investigating, but I am curious whether the
samples work.
What servlet container are you using? I have access to a Tru64 machine
running 4.0E (yours looks like 4.0G or so) and could possibly compare any
findings regarding the samples if you are running Tomcat.
Scott
-
I've seen something like that happen if you have multiple threads trying
to use the same Call object on the client side, which is not thread
safe.
-Peter
David Turner wrote:
>
> I've been battling with a "SOAPException-Parsing error" for quite some
> time now when trying to deploy a simple serv
31 matches
Mail list logo
