I know right now this only happens in a fit of developer incompetence(*),
but we may want to permit this. Assuming this is related to the bug I've
filed on this, I'm happy with it being in Axis1.1, but we may need to do
something else in axis1.2 for one-way messages.
-steve
(*) in my case some proto dispose() methods in things like messagecontext
kicking in too early.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, March 29, 2003 14:40
Subject: cvs commit: xml-axis/java/src/org/apache/axis/transport/http
AxisServlet.java
> dims 2003/03/29 14:40:25
>
> Modified: java/src/org/apache/axis/transport/http AxisServlet.java
> Log:
> Under some conditions the Response Message is null...Throw an exception
if this is the case.
>
> Revision Changes Path
> 1.159 +4 -0
xml-axis/java/src/org/apache/axis/transport/http/AxisServlet.java
>
> Index: AxisServlet.java
> ===================================================================
> RCS file:
/home/cvs/xml-axis/java/src/org/apache/axis/transport/http/AxisServlet.java,
v
> retrieving revision 1.158
> retrieving revision 1.159
> diff -u -r1.158 -r1.159
> --- AxisServlet.java 1 Feb 2003 21:03:01 -0000 1.158
> +++ AxisServlet.java 29 Mar 2003 22:40:25 -0000 1.159
> @@ -857,6 +857,10 @@
> t2=System.currentTimeMillis();
> }
> responseMsg = msgContext.getResponseMessage();
> + if (responseMsg == null) {
> + //tell everyone that something is wrong
> + throw new
Exception(Messages.getMessage("noResponse01"));
> + }
> } catch (AxisFault fault) {
> //log and sanitize
> processAxisFault(fault);
>
>
>
>
