[ http://issues.apache.org/jira/browse/AXIS2-333?page=all ]
Eran Chinthaka resolved AXIS2-333:
----------------------------------
Fix Version: 0.94
Resolution: Fixed
ServiceClient introduction has eliminated this.
> Non blocking dual client does not receive an error when an invalid service is
> specified in the target EPR
> ---------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-333
> URL: http://issues.apache.org/jira/browse/AXIS2-333
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: client-api
> Versions: 0.93, 0.94
> Reporter: Afkham Azeez
> Fix For: 0.94
>
> Tried to run the EchoNonBlockingClient example from the AXIS2 User Guide, and
> provided an invalid service name as part of the target EPR. The public void
> reportError(Exception e) method of the specified Callback object was not
> called. Instead, the
> while (!callback.isComplete()) {
> Thread.sleep(1000);
> }
> loop was running infinitely.
> However, when a correct service was specified, the same code works perfectly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
