axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George E. Turner (JIRA)" <>
Subject [jira] Created: (AXIS-2538) Support for one way operations is incompletely implemented
Date Wed, 09 Aug 2006 05:35:14 GMT
Support for one way operations is incompletely implemented

                 Key: AXIS-2538
             Project: Apache Axis
          Issue Type: Bug
          Components: Basic Architecture
    Affects Versions: 1.4
         Environment: tested using JDK1.5 (doesn't matter though)
            Reporter: George E. Turner

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 contact one of the administrators:
For more information on JIRA, see:


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

View raw message