You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Nick Gallardo (JIRA)" <ji...@apache.org> on 2006/07/19 17:59:13 UTC
[jira] Created: (AXIS2-909) JAXWS: Fix the invokeOneWay and
invokeAsync (callback) implementations in AxisInvocationController.
JAXWS: Fix the invokeOneWay and invokeAsync (callback) implementations in AxisInvocationController.
---------------------------------------------------------------------------------------------------
Key: AXIS2-909
URL: http://issues.apache.org/jira/browse/AXIS2-909
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: jaxws
Reporter: Nick Gallardo
I've implemented the invokeOneWay and invokeAsync-callback methods in the AxisInvocationController. The sync had already been implemented in a previous defect.
Also, I've updated the BaseDispatch to use this rather than the original AxisController. This brings us much closer to removing the AxisController API in favor of the AxisInvocationController. The changes to the async impl requires updates to the callbacks that are used. Specifically, the AsyncResponse/AsyncResponseProcessor have been renamed to be a little more intuitive.
The AsyncListener is the task that will wait for the async response to come back. This will be wrapped in an AsyncListenerWrapper that controls the starting and stopping. This AsyncListenerWrapper is what will be used by the JAX-WS client to determine if a response is available or not.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-909) JAXWS: Fix the invokeOneWay and
invokeAsync (callback) implementations in AxisInvocationController.
Posted by "Bill Nagy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-909?page=all ]
Bill Nagy resolved AXIS2-909.
-----------------------------
Resolution: Fixed
> JAXWS: Fix the invokeOneWay and invokeAsync (callback) implementations in AxisInvocationController.
> ---------------------------------------------------------------------------------------------------
>
> Key: AXIS2-909
> URL: http://issues.apache.org/jira/browse/AXIS2-909
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Nick Gallardo
> Assigned To: Bill Nagy
> Attachments: patch.txt
>
>
> I've implemented the invokeOneWay and invokeAsync-callback methods in the AxisInvocationController. The sync had already been implemented in a previous defect.
> Also, I've updated the BaseDispatch to use this rather than the original AxisController. This brings us much closer to removing the AxisController API in favor of the AxisInvocationController. The changes to the async impl requires updates to the callbacks that are used. Specifically, the AsyncResponse/AsyncResponseProcessor have been renamed to be a little more intuitive.
> The AsyncListener is the task that will wait for the async response to come back. This will be wrapped in an AsyncListenerWrapper that controls the starting and stopping. This AsyncListenerWrapper is what will be used by the JAX-WS client to determine if a response is available or not.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
deploy.wsdd created incorrectly
Posted by Deep Ghosh <de...@yahoo.com>.
All,
I have learned to live with this by now.
I am confused whether this is a bug or not.
I did the following.
1. Use wsdl2java to create some java files.
2. Compile and create a jar.
3. Put jar in axis folder.
4. deploy using AdminClient.
Nothing happens.
I removed the red portion and redeployed.
Now everything works.
Expanations?
Deep
<service name="AServiceSoap" provider="java:RPC" style="wrapped" use="literal">
<parameter name="wsdlTargetNamespace" value="http://tempuri.org/"/>
<parameter name="wsdlServiceElement" value="AServiceSoap"/>
<parameter name="schemaQualified" value="http://tempuri.org/"/>
<parameter name="wsdlServicePort" value="GloviaPrintService"/>
<parameter name="className" value="com.glovia.printservice.AServiceSoap_BindingImpl"/>
<parameter name="wsdlPortType" value="GloviaPrintSe
[jira] Assigned: (AXIS2-909) JAXWS: Fix the invokeOneWay and
invokeAsync (callback) implementations in AxisInvocationController.
Posted by "Bill Nagy (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-909?page=all ]
Bill Nagy reassigned AXIS2-909:
-------------------------------
Assignee: Bill Nagy
> JAXWS: Fix the invokeOneWay and invokeAsync (callback) implementations in AxisInvocationController.
> ---------------------------------------------------------------------------------------------------
>
> Key: AXIS2-909
> URL: http://issues.apache.org/jira/browse/AXIS2-909
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Nick Gallardo
> Assigned To: Bill Nagy
> Attachments: patch.txt
>
>
> I've implemented the invokeOneWay and invokeAsync-callback methods in the AxisInvocationController. The sync had already been implemented in a previous defect.
> Also, I've updated the BaseDispatch to use this rather than the original AxisController. This brings us much closer to removing the AxisController API in favor of the AxisInvocationController. The changes to the async impl requires updates to the callbacks that are used. Specifically, the AsyncResponse/AsyncResponseProcessor have been renamed to be a little more intuitive.
> The AsyncListener is the task that will wait for the async response to come back. This will be wrapped in an AsyncListenerWrapper that controls the starting and stopping. This AsyncListenerWrapper is what will be used by the JAX-WS client to determine if a response is available or not.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-909) JAXWS: Fix the invokeOneWay and
invokeAsync (callback) implementations in AxisInvocationController.
Posted by "Anonymous (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-909?page=all ]
Attachment: patch.txt
> JAXWS: Fix the invokeOneWay and invokeAsync (callback) implementations in AxisInvocationController.
> ---------------------------------------------------------------------------------------------------
>
> Key: AXIS2-909
> URL: http://issues.apache.org/jira/browse/AXIS2-909
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: jaxws
> Reporter: Nick Gallardo
> Attachments: patch.txt
>
>
> I've implemented the invokeOneWay and invokeAsync-callback methods in the AxisInvocationController. The sync had already been implemented in a previous defect.
> Also, I've updated the BaseDispatch to use this rather than the original AxisController. This brings us much closer to removing the AxisController API in favor of the AxisInvocationController. The changes to the async impl requires updates to the callbacks that are used. Specifically, the AsyncResponse/AsyncResponseProcessor have been renamed to be a little more intuitive.
> The AsyncListener is the task that will wait for the async response to come back. This will be wrapped in an AsyncListenerWrapper that controls the starting and stopping. This AsyncListenerWrapper is what will be used by the JAX-WS client to determine if a response is available or not.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org