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 "George E. Turner (JIRA)" <ax...@ws.apache.org> on 2006/08/09 07:35:14 UTC
[jira] Created: (AXIS-2538) Support for one way operations is
incompletely implemented
Support for one way operations is incompletely implemented
----------------------------------------------------------
Key: AXIS-2538
URL: http://issues.apache.org/jira/browse/AXIS-2538
Project: Apache Axis
Issue Type: Bug
Components: Basic Architecture
Affects Versions: 1.4
Environment: tested using JDK1.5 (doesn't matter though)
Reporter: George E. Turner
Attachments: axis-changes.zip
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 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] Commented: (AXIS-2538) Support for one way operations is
incompletely implemented
Posted by "Ortwin Glück (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466004 ]
Ortwin Glück commented on AXIS-2538:
------------------------------------
Response from George: "My apologies. I apparently submitted the file that also had that additional handling for a problem we were having with Axis receiving a oneway and throwing a NullPointerException from it when the sender was a WebLogic client that was handling it correctly. The code does not need to be there and you were correct in leaving it out."
The patch-take2.txt is without the NPE handling. Could any Axis developer comment on this patch, and schedule it for a release please?
> Support for one way operations is incompletely implemented
> ----------------------------------------------------------
>
> Key: AXIS-2538
> URL: https://issues.apache.org/jira/browse/AXIS-2538
> Project: Apache Axis
> Issue Type: Bug
> Components: Basic Architecture
> Affects Versions: 1.4
> Environment: tested using JDK1.5 (doesn't matter though)
> Reporter: George E. Turner
> 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 contact one of the administrators: https://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] Commented: (AXIS-2538) Support for one way operations is
incompletely implemented
Posted by "Ortwin Glück (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465817 ]
Ortwin Glück commented on AXIS-2538:
------------------------------------
Provided fix in patch format.
> Support for one way operations is incompletely implemented
> ----------------------------------------------------------
>
> Key: AXIS-2538
> URL: https://issues.apache.org/jira/browse/AXIS-2538
> Project: Apache Axis
> Issue Type: Bug
> Components: Basic Architecture
> Affects Versions: 1.4
> Environment: tested using JDK1.5 (doesn't matter though)
> Reporter: George E. Turner
> Attachments: axis-changes.zip, 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 contact one of the administrators: https://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: (AXIS-2538) Support for one way operations is
incompletely implemented
Posted by "Ortwin Glück (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ortwin Glück updated AXIS-2538:
-------------------------------
Attachment: patch.txt
> Support for one way operations is incompletely implemented
> ----------------------------------------------------------
>
> Key: AXIS-2538
> URL: https://issues.apache.org/jira/browse/AXIS-2538
> Project: Apache Axis
> Issue Type: Bug
> Components: Basic Architecture
> Affects Versions: 1.4
> Environment: tested using JDK1.5 (doesn't matter though)
> Reporter: George E. Turner
> Attachments: axis-changes.zip, 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 contact one of the administrators: https://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: (AXIS-2538) Support for one way operations is
incompletely implemented
Posted by "Ortwin Glück (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ortwin Glück updated AXIS-2538:
-------------------------------
Attachment: patch-take2.txt
> Support for one way operations is incompletely implemented
> ----------------------------------------------------------
>
> Key: AXIS-2538
> URL: https://issues.apache.org/jira/browse/AXIS-2538
> Project: Apache Axis
> Issue Type: Bug
> Components: Basic Architecture
> Affects Versions: 1.4
> Environment: tested using JDK1.5 (doesn't matter though)
> Reporter: George E. Turner
> 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 contact one of the administrators: https://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] Commented: (AXIS-2538) Support for one way operations is
incompletely implemented
Posted by "Ortwin Glück (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465815 ]
Ortwin Glück commented on AXIS-2538:
------------------------------------
George, what's this funny NullPointerException handling for?
> Support for one way operations is incompletely implemented
> ----------------------------------------------------------
>
> Key: AXIS-2538
> URL: https://issues.apache.org/jira/browse/AXIS-2538
> Project: Apache Axis
> Issue Type: Bug
> Components: Basic Architecture
> Affects Versions: 1.4
> Environment: tested using JDK1.5 (doesn't matter though)
> Reporter: George E. Turner
> Attachments: axis-changes.zip
>
>
> 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 contact one of the administrators: https://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