Hi Troy,
Please post the wire-dumps so we can see what is coming back.
Thanks,
-Matt
> -----Original Message-----
> From: Troy Beacleay [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 20, 2001 4:47 PM
> To: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
> Subject: .invoke(...) returns null from JSP
>
>
> Response resp = call.invoke (new URL( SOAPServerURL ), "blah blah" );
>
> Is in a test SOAP class, that works perfectly from a command line test
> harness. However, from a JSP page (tomcat 3.2) the line returns null and
> doesn't throw an exception. The invoke actually happens because I can see
> the request come through. My SOAP service is a Microsoft SOAP Toolkit 2.0
> implementation using an ASP front end; the advantage being that
> the included
> TraceUtility will intercept and display the SOAP request and
> response. The
> XML for the request comes in fine and the XML for the response is exactly
> what is expected...in both the command line harness and the JSP harness.
> The problem is that in the JSP harness this code in the Java class never
> executes because .invoke(...) returns null.
>
> // Check the response.
> if (resp.generatedFault ())
> {
> //Ouch, the call failed
> Fault fault = resp.getFault ();
> mCLR = fault.getFaultString();
> }
> else
> {
> mCLR = resp.getReturnValue().toString();
> }
>
> I would think that if a valid Response is not returned, it should throw an
> exception. In any case, has anyone seen and conquered this?
>
>
> Troy Beacleay
> Senior Systems Architect
> Software Development - Information Systems
> OFFICE: 281-465-1229
> http://www.splitrock.net
>
