[ 
https://issues.apache.org/jira/browse/AXIS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181232#comment-13181232
 ] 

Hudson commented on AXIS-2538:
------------------------------

Integrated in axis-trunk #37 (See 
[https://builds.apache.org/job/axis-trunk/37/])
    AXIS-2538: Properly serialize the mep attribute in server-config.wsdd.

veithen : 
Files : 
* 
/axis/axis1/java/trunk/axis/src/main/java/org/apache/axis/deployment/wsdd/WSDDOperation.java
* 
/axis/axis1/java/trunk/axis/src/main/java/org/apache/axis/description/OperationDesc.java

                
> Support for one way operations is incompletely implemented
> ----------------------------------------------------------
>
>                 Key: AXIS-2538
>                 URL: https://issues.apache.org/jira/browse/AXIS-2538
>             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
>             Fix For: 1.4.1
>
>         Attachments: axis-changes.zip, patch-take2.txt, patch.txt
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to