Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Date: Sun, 21 Oct 2012 20:28:12 +0000 (UTC)
From: "Andreas Veithen (JIRA)" <axis-dev@ws.apache.org>
To: java-dev@axis.apache.org
Message-ID: <1899687469.7718.1350851292665.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (AXIS-2538) Support for one way operations is
 incompletely implemented
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Veithen updated AXIS-2538:
----------------------------------

    Labels: oneway  (was: )
    
> 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
>              Labels: oneway
>             Fix For: 1.4.1
>
>         Attachments: ASF.LICENSE.NOT.GRANTED--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
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org