Client-side processing of asynchronous requests with void return type is flawed.
--------------------------------------------------------------------------------
Key: AXIS2-3476
URL: https://issues.apache.org/jira/browse/AXIS2-3476
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.2, 1.3, 1.4
Environment: Axis2 1.3, Java 6, Windows XP
Reporter: Aaron Gourley
Root of problem is in
modules/codegen/src/org/apache/axis2/wsdl/template/java/InterfaceImplementation.xsl,
near the following block of code:
<xsl:when test="$outputtype=''">
// Nothing to pass as the callback!!!
</xsl:when>
Due to the fact that the startXXX() methods don't register a callback in the
operationClient for void methods, generated client stubs are produced in such a
way that there is no way for the client application to have itself notified
upon request completion (whether on error, fault, or otherwise). The client is
left in limbo.
Along with a fix for this issue I believe that a change has to be made to the
CallbackHandlerTemplate.xsl file so that generated callback handlers support
some sort of onComplete() derivation (such as receiveCompleteXXX). The reason
being is that for void methods there is no way for a client application using
the generated stub code to be notified when a void method completes
successfully. This way, the generated Axis2Callback within the stub code would
be able to call the new onComplete() style method in the CallbackHandler,
allowing the client app to know when execution is complete.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
