axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Javier Kohen (JIRA)" <>
Subject [jira] Updated: (AXIS2-2113) Async. invocation error not using exception class from databinding
Date Mon, 30 Jul 2007 18:23:53 GMT


Javier Kohen updated AXIS2-2113:


Test case updated to work with Axis 1.2.

You can use netcat to avoid having to load the service. I use it like this: nc6 -l -p 8080
--continuous --exec="cat response.http"

Here, response.http was generated by capturing the service's traffic.

> Async. invocation error not using exception class from databinding
> ------------------------------------------------------------------
>                 Key: AXIS2-2113
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: databinding
>    Affects Versions: 1.1.1
>         Environment: Java 6. Using Axis2 server to host the webservice.
>            Reporter: Javier Kohen
>            Assignee: Amila Chinthaka Suriarachchi
>         Attachments:
> When using async. service invocation on the client side, exceptions are not passed as
the databinding-specified class, but as AxisFault instances.
> The attached test case is a slightly modified version of the XMLBeans quick start example,
so that it always returns a fault when the service is invoked. The included client will try
both an async. and a sync. invocation of the service. It is expected that both will show "code=code;
string=string," meaning that the ServiceDownMessageException class was recognized as such,
but in my tests only the sync. code works as expected.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message