Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
X-SEF-567C2F8B-1BA6-483D-AE96-D486511D77B: 1
Received: from Unknown [10.132.64.95] by adeln128.originenergy.com.au -
 SurfControl E-mail Filter (5.0); Thu, 27 Apr 2006 15:53:19 +0930
Received: from melbm001.originenergy.com.au ([10.80.64.27]) by
 adelm001.originenergy.com.au with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 27 Apr 2006 15:53:19 +0930
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Subject: [Axis2] RE: Client-within-server problems
Date: Thu, 27 Apr 2006 16:23:19 +1000
Message-ID: 
 <149A63E372B682408396757BE5AA6CE1C6EC3D@melbm001.originenergy.com.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Axis2] RE: Client-within-server problems
Thread-Index: AcZpA2SuXCV+7pr6SiuxYjbfAeVKrQAvxG2w
From: "Marshall, John" <John.Marshall@originenergy.com.au>
To: <axis-user@ws.apache.org>
X-OriginalArrivalTime: 27 Apr 2006 06:23:19.0448 (UTC)
 FILETIME=[13918180:01C669C3]
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Finally solved my own problem, the system at the other end was not a
proper Web Service and wasn't actually running anything resembling the
WSDL I'd been given. It was more of an HTTP listener that someone had
set up to monitor the traffic.

I created a dummy web service to simulate the other end and my
AxisService immediately cheered up and started working great!


Hi,
I'm trying to develop a request-reply web service, rather like in Figure
4 on this website:

http://www-128.ibm.com/developerworks/library/ws-asynch2/

To do this I'm essentially writing a synchronous web service to do the
first request-ack interaction. During the processing I launch a new
thread that is effectively a client for the other end. I want to send
the response document (which may have taken some time to obtain) back to
the other end.

I have the WSDL of the other end and used it to create a client stub. I
can send my response document to the other end and get the ack back from
it. However, my Stub ALWAYS crashes within the=20
_operationClient.execute(true);

With a NullPointerException.=20
I've dug around a bit and it seems to be caused by the
createSOAPMessage() method of the TransportUtils class - the inStream is
always null.

I'm guessing there is something clever I have to do with
message/operation/configuration contexts, but I can't figure it out! The
really weird thing is that despite the AxisFault being thrown, the
document still gets sent!

Can anyone advise what I have to do to be able to behave like a client
within an AxisService?

Thanks for any light you can shed,
John M.