Weird errors

[Dennis Faynberg <de...@nj.paradyne.com>]

Hi, all.
	
I'm trying to install soap-2_0 on my linux os.
I am using tomcat as a 1.1 servlet container.
I am getting really weird error on the client
side at response arrival stage.
here is the stack trace:
$ java samples.addressbook.GetAddress 
 http://localhost:2020/soap/servlet/rpcrouter "John B. Good"
java.lang.ArrayIndexOutOfBoundsException: 
	at java.io.BufferedReader.read(BufferedReader.java:100)
	at java.io.BufferedReader.refillBuffer(BufferedReader.java:165)
	at java.io.BufferedReader.readLine(BufferedReader.java:131)
	at
org.apache.soap.util.IOUtils.getStringFromReader(IOUtils.java:83)
	at org.apache.soap.rpc.Call.invoke(Call.java:154)
	at samples.addressbook.GetAddress.main(GetAddress.java:125)

what creeps me out is that the exception is floating up from 
java.io.BufferedReader method and not from your(apache) code.
as proof that error occures during retrieving http response body
tcp trace (using your TcpTunnel).
oh yeah, never mind the fault response from the soap router.
I know I did't deploy any services yet.
(this might have something to do with the fact that deployed services
db get wiped clean if servlet container goes down abruptly :-( there 
must be a better way to treat config records, booo)
>>>>>>>>>>>>>>>>>>

POST /soap/servlet/rpcrouter HTTP/1.0
Host: localhost:2020
Content-Type: text/xml
Content-Length: 444
SOAPAction: ""

<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:getAddressFromName xmlns:ns1="urn:AddressFetcher"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<nameToLookup xsi:type="xsd:string">John B. Good</nameToLookup>
</ns1:getAddressFromName>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

HTTP/1.0 500 Internal Server Error
Content-Length: 418
Date: Wed, 18 Oct 2000 16:02:19 GMT
Servlet-Engine: Tomcat Web Server/3.1 (JSP 1.1; Servlet 2.2; Java 1.2.2;
 Linux 2.2.12-20 i386; java.vendor=Sun Microsystems Inc.)
Set-Cookie: JSESSIONID=To1017mC7844221550852218At;Path=/soap
Set-Cookie2: 
 JSESSIONID=To1017mC7844221550852218At;Version=1;Discard;Path="/soap"
Content-Language: en
Content-Type: text/xml; charset=UTF-8
Status: 500

<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>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>service 'urn:AddressFetcher' unknown</faultstring>
<faultactor>/soap/servlet/rpcrouter</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

>>>>>>>>>>>>

ps: The whole Xerces v.s. Sun's ProjectX thing that one comes up against 
while installing apache soap is a nightmare. If one is using j2ee
framework (and jars : )) the classpath set up becomes an infinite play of
classpath settings and script modifications, especially if j2ee user does
not know that j2ee.jar includes dom level 1 interfaces (the person who put
them there should be shoot). Essentially while installing soap on top of 
j2ee, be expected to deal with #@$#@$#@$@**&^%#@ 3 diff. parsers:
Xerces, ProjectX(Sun), JAXP(Sun).