[AXIS-2538] Support for one way operations is incompletely implemented

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.4
• Fix Version/s: 1.4.1
• Component/s: Basic Architecture
• Labels: oneway
• Environment: tested using JDK1.5 (doesn't matter though)
• Assignee: Andreas Veithen
• Reporter: George E. Turner
• Created: 09/Aug/06 05:33
• Updated: 21/Oct/12 20:27

Description

Several pieces are missing from the implementation to get one wau working correctly, and the invokeOneWay method in Call.java 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 Call.java, JavaSkelWriter.java, and JavaStubWriter.java 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.