SOAPSMTPConnection / Call code issue, possible bug?

[bh...@isochron.com]

Is it my imagination, or is there a nullPointerException bug when you use
SOAPSMTPConnection as the transport, and execute Call:call.invoke()?  I
traced through the code, and after the message is sent out(successfully),
the method tries to automatically get a response.  It tries to get the
response context, but it is never initialized in SOAPSMTPConnection.  (oddly
enough, it never seems to complain about it not being initialized either)
Anyhow, it then tries to execute a method(line 163 of Call.java) on that
class, which throws a nullPointerException.  I wouldn't expect it to have a
whole lot to say, since SMTP isn't going to just block and wait for a
response, but I would think it should have SOME sort of successful response
or something.  

Am I missing something?  Is there an official, recognized fix for this(other
than me hacking in a solution?)  Thanks.

Barry Hobbs