Thanks Bill.

If you could file this in the JIRA bug system, this information won't
get lost.

See http://ws.apache.org/axis/bugs.html


--
Tom Jordahl

-----Original Message-----
From: Bill Kuker [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, October 10, 2007 1:39 PM
To: axis-dev@ws.apache.org
Subject: Minor bug & fix in SOAPMonitor from AXIS 1.4

There is a minor bug in SOAPMonitor applet. If you start it after a
request has come in, but before the response gets sent back, the
SOAPMonitorHandler sends the response to the applet, which can't find a
request and disconnects, saying "The server communication has been
terminated."

The following function throws a NullPointerException trying to get the
id value. For clarity I've just included the fix in context. The stderr
output is clearly not necessary.

        /**
         * Find the data for a given id
         */
        public SOAPMonitorData findData(Long id) {
            SOAPMonitorData soap = null;
            for (int row=data.size(); (row > 0) && (soap == null);
row--) {
                soap = (SOAPMonitorData) data.elementAt(row-1);

                //NEW CODE
                if ( soap == null || soap.getId() == null ){
                        System.err.println("Never saw a request to match
this response.");
                        return null;
                }
                //END NEW CODE

                if (soap.getId().longValue() != id.longValue()) {
                    soap = null;
                }
            }
            return soap;
        }


Thanks AXIS folks for a great library!

-Bill Kuker

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to