Hi William,

When you invoke the service using fireAndForget you need to put put a
sleep statement after invocation, if you do not do that the main thread
terminate before sending  the message.
> Has anyone had success writing an In-Only client that they'd be willing to 
> share?  I've deployed a simple In-Only service on WebSphere that works fine 
> via soapui, but when I try to invoke it via a Java client it doesn't run, 
> completely.  That is, I can see the log4j trace with additional activity 
> after the usual ending "Exiting deleteAttachments()" entry. I know it doesn't 
> completely run (which I know sounds strange) because I have another service 
> for interrogating the static variable it initializes.   Using tcpmon I'm not 
> seeing any significant difference in the SOAP messages, which I've 
> constructed "manually" or via Axiom APIs based on what I see soapui sending.  
> I've tried using fireAndForget and robustSend along with stub invocation 
> (equivalent of the Axis2 generated test case), the latter fails with 
> AxisFault: The input stream for an incoming message is null.
>
> Thanks,
> William
>
>
>
>
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by anyone else
> is unauthorized. If you are not the intended recipient, any disclosure,
> copying, distribution or any action taken or omitted to be taken in reliance
> on it, is prohibited and may be unlawful. If you are not the intended
> addressee please contact the sender and dispose of this e-mail. Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>   


-- 
"If we knew what it was we were doing, it would not be called research, would 
it?" - Albert Einstein


http://blogs.deepal.org
http://deepal.org


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to