You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Jason Wells <ja...@semanticresearch.com> on 2002/05/30 20:43:48 UTC
Further along, new problem...
Hi,
I'm still struggling to get a helloworld SOAP service/client combo
going. I've gotten a little farther than yesterday, but now when I call
call.invoke(), the client gives me this stack trace:
java.lang.NullPointerException
at
org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
at org.apache.soap.util.net.HTTPUtils.post(HTTPUtils.java:333)
at
org.apache.soap.transport.http.SOAPHTTPConnection.send
(SOAPHTTPConnection.java:282)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at hello.Client.main(Unknown Source)
Meanwhile, I get this stack trace from Tomcat:
java.lang.NullPointerException
at
org.apache.soap.server.SOAPFaultRouter.notifyListeners(SOAPFaultRouter.java:
101)
at
org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:
304)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:
246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:
174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:
1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:536)
I believe everything is in order; the service, client, and descriptor
look fine. Any idea why I'd get this?
Thanks,
Jason
Re: Further along, new problem... solved!
Posted by John Miller Crawford <jm...@websight.co.nz>.
Well, never assume anything! I had assumed TcpTunnelGui would give me the
same result as Jason got. When I tried it, Tomcat threw up an error 500,
just the same as Jason -- but for a different cause. It was produced by a
NoClasssDefFound and the reason for that was that somehow, I'd managed to
drop activation.jar out of Tomcat's classpath. With that back in there, I
was back in business.
So there really was "some stupidly simple answer" as I suspected.
So, thanks guys (Erich and Jason in particular), for showing me the path I
needed to go down!
John
----- Original Message -----
From: John Miller Crawford
To: soap-user@xml.apache.org
Sent: Saturday, 1 June 2002 11:01
Subject: Re: Further along, new problem...
As a SOAP newbie, I have an identical problem to Jason's, but I'm afraid his
solution doesn't work for me:
>> when I installed Apache SOAP, I followed method 2, which has you create
>> a context based on the non-WAR /soap directory. This doesn't work. You
>> must use the WAR file
I did use deployment method 1, putting the WAR file in
%tomcat_home%/webapps.
However, I still get the identical NullPointerException that vexed Jason:
java.lang.NullPointerException
at
org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
at org.apache.soap.util.net.HTTPUtils.post(HTTPUtils.java:333)
at org.apache.soap.transport.http.SOAPHTTPConnection.send
(SOAPHTTPConnection.java:282)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at GetMessage.main(GetMessage.java:43)
(Apache SOAP Admin shows that the service that GetMessage is calling is
deployed.)
I haven't used TcpTunnelGui yet -- I'm assuming I'd get the same result as
Jason got and there's some stupidly simple answer -- is there?
TIA
John
Re: Further along, new problem... solved!
Posted by John Miller Crawford <jm...@websight.co.nz>.
Well, never assume anything! I had assumed TcpTunnelGui would give me the
same result as Jason got. When I tried it, Tomcat threw up an error 500,
just the same as Jason -- but for a different cause. It was produced by a
NoClasssDefFound and the reason for that was that somehow, I'd managed to
drop activation.jar out of Tomcat's classpath. With that back in there, I
was back in business.
So there really was "some stupidly simple answer" as I suspected.
So, thanks guys (Erich and Jason in particular), for showing me the path I
needed to go down!
John
----- Original Message -----
From: John Miller Crawford
To: soap-user@xml.apache.org
Sent: Saturday, 1 June 2002 11:01
Subject: Re: Further along, new problem...
As a SOAP newbie, I have an identical problem to Jason's, but I'm afraid his
solution doesn't work for me:
>> when I installed Apache SOAP, I followed method 2, which has you create
>> a context based on the non-WAR /soap directory. This doesn't work. You
>> must use the WAR file
I did use deployment method 1, putting the WAR file in
%tomcat_home%/webapps.
However, I still get the identical NullPointerException that vexed Jason:
java.lang.NullPointerException
at
org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
at org.apache.soap.util.net.HTTPUtils.post(HTTPUtils.java:333)
at org.apache.soap.transport.http.SOAPHTTPConnection.send
(SOAPHTTPConnection.java:282)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at GetMessage.main(GetMessage.java:43)
(Apache SOAP Admin shows that the service that GetMessage is calling is
deployed.)
I haven't used TcpTunnelGui yet -- I'm assuming I'd get the same result as
Jason got and there's some stupidly simple answer -- is there?
TIA
John
Re: Further along, new problem...
Posted by John Miller Crawford <jm...@websight.co.nz>.
As a SOAP newbie, I have an identical problem to Jason's, but I'm afraid his
solution doesn't work for me:
>> when I installed Apache SOAP, I followed method 2, which has you create
>> a context based on the non-WAR /soap directory. This doesn't work. You
>> must use the WAR file
I did use deployment method 1, putting the WAR file in
%tomcat_home%/webapps.
However, I still get the identical NullPointerException that vexed Jason:
java.lang.NullPointerException
at
org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
at org.apache.soap.util.net.HTTPUtils.post(HTTPUtils.java:333)
at org.apache.soap.transport.http.SOAPHTTPConnection.send
(SOAPHTTPConnection.java:282)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at GetMessage.main(GetMessage.java:43)
(Apache SOAP Admin shows that the service that GetMessage is calling is
deployed.)
I haven't used TcpTunnelGui yet -- I'm assuming I'd get the same result as
Jason got and there's some stupidly simple answer -- is there?
TIA
John
Re: Further along, new problem...
Posted by John Miller Crawford <jm...@websight.co.nz>.
As a SOAP newbie, I have an identical problem to Jason's, but I'm afraid his
solution doesn't work for me:
>> when I installed Apache SOAP, I followed method 2, which has you create
>> a context based on the non-WAR /soap directory. This doesn't work. You
>> must use the WAR file
I did use deployment method 1, putting the WAR file in
%tomcat_home%/webapps.
However, I still get the identical NullPointerException that vexed Jason:
java.lang.NullPointerException
at
org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
at org.apache.soap.util.net.HTTPUtils.post(HTTPUtils.java:333)
at org.apache.soap.transport.http.SOAPHTTPConnection.send
(SOAPHTTPConnection.java:282)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at GetMessage.main(GetMessage.java:43)
(Apache SOAP Admin shows that the service that GetMessage is calling is
deployed.)
I haven't used TcpTunnelGui yet -- I'm assuming I'd get the same result as
Jason got and there's some stupidly simple answer -- is there?
TIA
John
Re: Further along, new problem...
Posted by Jason Wells <ja...@semanticresearch.com>.
Ok, finally figured out what is up with my SOAP helloworld. Basically,
when I installed Apache SOAP, I followed method 2, which has you create
a context based on the non-WAR /soap directory. This doesn't work. You
must use the WAR file. If you don't, you get into all kinds of fun, at
least in this configuration.
Anyway, thanks for the help.
Jason
Re: Further along, new problem...
Posted by Jason Wells <ja...@semanticresearch.com>.
Ok, finally figured out what is up with my SOAP helloworld. Basically,
when I installed Apache SOAP, I followed method 2, which has you create
a context based on the non-WAR /soap directory. This doesn't work. You
must use the WAR file. If you don't, you get into all kinds of fun, at
least in this configuration.
Anyway, thanks for the help.
Jason
Re: Further along, new problem...
Posted by Jason Wells <ja...@semanticresearch.com>.
Yeah. This is the response:
HTTP/1.1 500 Internal Server Error
Connection: close
Set-Cookie: JSESSIONID=130C49D8EC449AF750CE2E796B898460;Path=/soap
<html><head><title>Apache Tomcat/4.0.3 - Error
report</title><STYLE><!--H1{font-family : sans-
serif,Arial,Tahoma;color : white;background-color : #0086b2;}
BODY{font-family : sans-serif,Arial,Tahoma;color :
black;background-color : white;} B{color : white;background-color :
#0086b2;} HR{color : #0086b2;} --></STYLE> </head><body><h1>Apache
Tomcat/4.0.3 - HTTP Status 500 - Internal Server Error</h1><HR size="1"
noshade><p><b>type</b> Exception report</p><p><b>message</b> <u>Internal
Server Error</u></p><p><b>description</b> <u>The server encountered an
internal error (Internal Server Error) that prevented it from fulfilling
this request.</u></p><p><b>exception</b>
<pre>javax.servlet.ServletException: Error building response envelope:
java.lang.NullPointerException
at
org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:
353)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:
246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:
174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:
1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:496)
</pre></p><HR size="1" noshade></body></html>
As you can tell from the stack trace, I'm running this in Tomcat 4.0.3.
Is this a problem?
Jason
On Thursday, May 30, 2002, at 02:33 PM, Erich Izdepski wrote:
> Do you see a response in the tunnel tool? The stack trace indicated the
> response had been returned from your service. You could a printly to the
> service to see if it is being called or not.
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
Re: Further along, new problem...
Posted by Jason Wells <ja...@semanticresearch.com>.
Yeah. This is the response:
HTTP/1.1 500 Internal Server Error
Connection: close
Set-Cookie: JSESSIONID=130C49D8EC449AF750CE2E796B898460;Path=/soap
<html><head><title>Apache Tomcat/4.0.3 - Error
report</title><STYLE><!--H1{font-family : sans-
serif,Arial,Tahoma;color : white;background-color : #0086b2;}
BODY{font-family : sans-serif,Arial,Tahoma;color :
black;background-color : white;} B{color : white;background-color :
#0086b2;} HR{color : #0086b2;} --></STYLE> </head><body><h1>Apache
Tomcat/4.0.3 - HTTP Status 500 - Internal Server Error</h1><HR size="1"
noshade><p><b>type</b> Exception report</p><p><b>message</b> <u>Internal
Server Error</u></p><p><b>description</b> <u>The server encountered an
internal error (Internal Server Error) that prevented it from fulfilling
this request.</u></p><p><b>exception</b>
<pre>javax.servlet.ServletException: Error building response envelope:
java.lang.NullPointerException
at
org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:
353)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:
246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:
174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:
1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:496)
</pre></p><HR size="1" noshade></body></html>
As you can tell from the stack trace, I'm running this in Tomcat 4.0.3.
Is this a problem?
Jason
On Thursday, May 30, 2002, at 02:33 PM, Erich Izdepski wrote:
> Do you see a response in the tunnel tool? The stack trace indicated the
> response had been returned from your service. You could a printly to the
> service to see if it is being called or not.
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
RE: Further along, new problem...
Posted by Erich Izdepski <ei...@cysive.com>.
Do you see a response in the tunnel tool? The stack trace indicated the
response had been returned from your service. You could a printly to the
service to see if it is being called or not.
Erich Izdepski
Senior Software Engineer
Cysive, Inc.
-----Original Message-----
From: Jason Wells [mailto:jason@semanticresearch.com]
Sent: Thursday, May 30, 2002 5:23 PM
To: soap-user@xml.apache.org
Subject: Re: Further along, new problem...
After some further debugging, I'm reaching the conclusion that the
content type is okay. I set up TcpTunnelGui. This is the SOAP request my
client is generating:
POST HTTP/1.0
Host: localhost
Content-Type: text/xml; charset=utf-8
Content-Length: 447
SOAPAction: ""
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:getMessage xmlns:ns1="urn:helloworld" SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<caller xsi:type="xsd:string">reader</caller>
</ns1:getMessage>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
So the content type is set to "text/xml", which looks good to me.
Anything look wrong with this?
Thanks,
Jason
On Thursday, May 30, 2002, at 01:47 PM, Erich Izdepski wrote:
> In the soap samples directory look at mime/MimeTest.java and the
> sendFile
> method. Normally a service wouldn't have to set this. By the way, the
> null
> pointer you are hitting
> should have been thrown as a different exception by the apache code (it
> is a
> bug).
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
RE: Further along, new problem...
Posted by Erich Izdepski <ei...@cysive.com>.
Do you see a response in the tunnel tool? The stack trace indicated the
response had been returned from your service. You could a printly to the
service to see if it is being called or not.
Erich Izdepski
Senior Software Engineer
Cysive, Inc.
-----Original Message-----
From: Jason Wells [mailto:jason@semanticresearch.com]
Sent: Thursday, May 30, 2002 5:23 PM
To: soap-user@xml.apache.org
Subject: Re: Further along, new problem...
After some further debugging, I'm reaching the conclusion that the
content type is okay. I set up TcpTunnelGui. This is the SOAP request my
client is generating:
POST HTTP/1.0
Host: localhost
Content-Type: text/xml; charset=utf-8
Content-Length: 447
SOAPAction: ""
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:getMessage xmlns:ns1="urn:helloworld" SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<caller xsi:type="xsd:string">reader</caller>
</ns1:getMessage>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
So the content type is set to "text/xml", which looks good to me.
Anything look wrong with this?
Thanks,
Jason
On Thursday, May 30, 2002, at 01:47 PM, Erich Izdepski wrote:
> In the soap samples directory look at mime/MimeTest.java and the
> sendFile
> method. Normally a service wouldn't have to set this. By the way, the
> null
> pointer you are hitting
> should have been thrown as a different exception by the apache code (it
> is a
> bug).
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
Re: Further along, new problem...
Posted by Jason Wells <ja...@semanticresearch.com>.
After some further debugging, I'm reaching the conclusion that the
content type is okay. I set up TcpTunnelGui. This is the SOAP request my
client is generating:
POST HTTP/1.0
Host: localhost
Content-Type: text/xml; charset=utf-8
Content-Length: 447
SOAPAction: ""
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:getMessage xmlns:ns1="urn:helloworld" SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<caller xsi:type="xsd:string">reader</caller>
</ns1:getMessage>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
So the content type is set to "text/xml", which looks good to me.
Anything look wrong with this?
Thanks,
Jason
On Thursday, May 30, 2002, at 01:47 PM, Erich Izdepski wrote:
> In the soap samples directory look at mime/MimeTest.java and the
> sendFile
> method. Normally a service wouldn't have to set this. By the way, the
> null
> pointer you are hitting
> should have been thrown as a different exception by the apache code (it
> is a
> bug).
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
Re: Further along, new problem...
Posted by Jason Wells <ja...@semanticresearch.com>.
After some further debugging, I'm reaching the conclusion that the
content type is okay. I set up TcpTunnelGui. This is the SOAP request my
client is generating:
POST HTTP/1.0
Host: localhost
Content-Type: text/xml; charset=utf-8
Content-Length: 447
SOAPAction: ""
<?xml version='1.0' encoding='UTF-8'?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<ns1:getMessage xmlns:ns1="urn:helloworld" SOAP-
ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<caller xsi:type="xsd:string">reader</caller>
</ns1:getMessage>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
So the content type is set to "text/xml", which looks good to me.
Anything look wrong with this?
Thanks,
Jason
On Thursday, May 30, 2002, at 01:47 PM, Erich Izdepski wrote:
> In the soap samples directory look at mime/MimeTest.java and the
> sendFile
> method. Normally a service wouldn't have to set this. By the way, the
> null
> pointer you are hitting
> should have been thrown as a different exception by the apache code (it
> is a
> bug).
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
RE: Further along, new problem...
Posted by Erich Izdepski <ei...@cysive.com>.
In the soap samples directory look at mime/MimeTest.java and the sendFile
method. Normally a service wouldn't have to set this. By the way, the null
pointer you are hitting
should have been thrown as a different exception by the apache code (it is a
bug).
Erich Izdepski
Senior Software Engineer
Cysive, Inc.
-----Original Message-----
From: Jason Wells [mailto:jason@semanticresearch.com]
Sent: Thursday, May 30, 2002 4:16 PM
To: soap-user@xml.apache.org
Subject: Re: Further along, new problem...
Erich,
How does the service set this? Can you show me an example?
Thanks again,
Jason
On Thursday, May 30, 2002, at 12:20 PM, Erich Izdepski wrote:
> Jason-
> The problem from
> org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
> is that the content type is null. Your service is not setting the
> content
> type, causing the null pointer. That's where I'd look.
>
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
RE: Further along, new problem...
Posted by Erich Izdepski <ei...@cysive.com>.
In the soap samples directory look at mime/MimeTest.java and the sendFile
method. Normally a service wouldn't have to set this. By the way, the null
pointer you are hitting
should have been thrown as a different exception by the apache code (it is a
bug).
Erich Izdepski
Senior Software Engineer
Cysive, Inc.
-----Original Message-----
From: Jason Wells [mailto:jason@semanticresearch.com]
Sent: Thursday, May 30, 2002 4:16 PM
To: soap-user@xml.apache.org
Subject: Re: Further along, new problem...
Erich,
How does the service set this? Can you show me an example?
Thanks again,
Jason
On Thursday, May 30, 2002, at 12:20 PM, Erich Izdepski wrote:
> Jason-
> The problem from
> org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
> is that the content type is null. Your service is not setting the
> content
> type, causing the null pointer. That's where I'd look.
>
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
Re: Further along, new problem...
Posted by Jason Wells <ja...@semanticresearch.com>.
Erich,
How does the service set this? Can you show me an example?
Thanks again,
Jason
On Thursday, May 30, 2002, at 12:20 PM, Erich Izdepski wrote:
> Jason-
> The problem from
> org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
> is that the content type is null. Your service is not setting the
> content
> type, causing the null pointer. That's where I'd look.
>
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
Re: Further along, new problem...
Posted by Jason Wells <ja...@semanticresearch.com>.
Erich,
How does the service set this? Can you show me an example?
Thanks again,
Jason
On Thursday, May 30, 2002, at 12:20 PM, Erich Izdepski wrote:
> Jason-
> The problem from
> org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
> is that the content type is null. Your service is not setting the
> content
> type, causing the null pointer. That's where I'd look.
>
>
> Erich Izdepski
> Senior Software Engineer
> Cysive, Inc.
RE: Further along, new problem...
Posted by Erich Izdepski <ei...@cysive.com>.
Jason-
The problem from
org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
is that the content type is null. Your service is not setting the content
type, causing the null pointer. That's where I'd look.
Erich Izdepski
Senior Software Engineer
Cysive, Inc.
-----Original Message-----
From: Jason Wells [mailto:jason@semanticresearch.com]
Sent: Thursday, May 30, 2002 2:44 PM
To: soap-user@xml.apache.org
Subject: Further along, new problem...
Hi,
I'm still struggling to get a helloworld SOAP service/client combo
going. I've gotten a little farther than yesterday, but now when I call
call.invoke(), the client gives me this stack trace:
java.lang.NullPointerException
at
org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
at org.apache.soap.util.net.HTTPUtils.post(HTTPUtils.java:333)
at
org.apache.soap.transport.http.SOAPHTTPConnection.send
(SOAPHTTPConnection.java:282)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at hello.Client.main(Unknown Source)
Meanwhile, I get this stack trace from Tomcat:
java.lang.NullPointerException
at
org.apache.soap.server.SOAPFaultRouter.notifyListeners(SOAPFaultRouter.java:
101)
at
org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:
304)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:
246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170
)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:
174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:
1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107
)
at java.lang.Thread.run(Thread.java:536)
I believe everything is in order; the service, client, and descriptor
look fine. Any idea why I'd get this?
Thanks,
Jason
RE: Further along, new problem...
Posted by Erich Izdepski <ei...@cysive.com>.
Jason-
The problem from
org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
is that the content type is null. Your service is not setting the content
type, causing the null pointer. That's where I'd look.
Erich Izdepski
Senior Software Engineer
Cysive, Inc.
-----Original Message-----
From: Jason Wells [mailto:jason@semanticresearch.com]
Sent: Thursday, May 30, 2002 2:44 PM
To: soap-user@xml.apache.org
Subject: Further along, new problem...
Hi,
I'm still struggling to get a helloworld SOAP service/client combo
going. I've gotten a little farther than yesterday, but now when I call
call.invoke(), the client gives me this stack trace:
java.lang.NullPointerException
at
org.apache.soap.transport.TransportMessage.read(TransportMessage.java:206)
at org.apache.soap.util.net.HTTPUtils.post(HTTPUtils.java:333)
at
org.apache.soap.transport.http.SOAPHTTPConnection.send
(SOAPHTTPConnection.java:282)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at hello.Client.main(Unknown Source)
Meanwhile, I get this stack trace from Tomcat:
java.lang.NullPointerException
at
org.apache.soap.server.SOAPFaultRouter.notifyListeners(SOAPFaultRouter.java:
101)
at
org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:
304)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:
246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170
)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:
174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:
566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:
1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107
)
at java.lang.Thread.run(Thread.java:536)
I believe everything is in order; the service, client, and descriptor
look fine. Any idea why I'd get this?
Thanks,
Jason