axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Updated] (AXIS-2538) Support for one way operations is incompletely implemented
Date Sun, 21 Oct 2012 20:28:12 GMT


Andreas Veithen updated AXIS-2538:

    Labels: oneway  (was: )
> Support for one way operations is incompletely implemented
> ----------------------------------------------------------
>                 Key: AXIS-2538
>                 URL:
>             Project: Axis
>          Issue Type: Bug
>          Components: Basic Architecture
>    Affects Versions: 1.4
>         Environment: tested using JDK1.5 (doesn't matter though)
>            Reporter: George E. Turner
>            Assignee: Andreas Veithen
>              Labels: oneway
>             Fix For: 1.4.1
>         Attachments:, patch-take2.txt, patch.txt
> Several pieces are missing from the implementation to get one wau working correctly,
and the invokeOneWay method in incorrectly runs in a background thread.  SOAP oneway
does NOT imply async handling, it just means that the client cannot send a response "object"
or throw and Exception.  This means that a oneway operation cannot define a fault or an output,
not that it is performed asyncronously.  The invokeOneWayEngine needs the background thread
removed so that the call will block until completion.
> The next missing piece is that the AdminClient fails to add the "mep=oneway" to the operation
when it exists in the deploy.wsdd to the server-config.wsdd.
> The next missing piece is that when the skeletonDeploy switch is used, the setMep(OperationType.ONE_WAY)
is not inserted into the generated code for iether a client or server side generation using
wsdl2java.  I am attaching code changes for,, and
that has been tested to fix the noted problems.  The only fix not provided is for the AdminClient,
as I just inserted the missing line into the server-config.wsdd manually to fix my problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message