You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Milinda Lakmal Pathirage (JIRA)" <ji...@apache.org> on 2007/01/05 07:34:27 UTC
[jira] Created: (AXIS2C-492) Wrong Logic inside generate service
skeleton's axis2_svc_skel__invoke function (WSDL2C Java
Version)
Wrong Logic inside generate service skeleton's axis2_svc_skel_<Service Name>_invoke function (WSDL2C Java Version)
-------------------------------------------------------------------------------------------------------------------
Key: AXIS2C-492
URL: https://issues.apache.org/jira/browse/AXIS2C-492
Project: Axis2-C
Issue Type: Bug
Components: code generation
Affects Versions: Current (Nightly)
Reporter: Milinda Lakmal Pathirage
In the current implementation of generated code, when we execute the invoke method of the service skeleton it select the correct operation by getting the local name of the root xml element of the payload. But this case is only succeed when we use RPC style binding. Have to correct the operation selection logic by getting the operation name from the message context.
--
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Updated: (AXIS2C-492) Wrong Logic inside generate service
skeleton's axis2_svc_skel__invoke function (WSDL2C Java
Version)
Posted by "Milinda Lakmal Pathirage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milinda Lakmal Pathirage updated AXIS2C-492:
--------------------------------------------
Attachment: svcskeltemplate.patch
> Wrong Logic inside generate service skeleton's axis2_svc_skel_<Service Name>_invoke function (WSDL2C Java Version)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-492
> URL: https://issues.apache.org/jira/browse/AXIS2C-492
> Project: Axis2-C
> Issue Type: Bug
> Components: code generation
> Affects Versions: Current (Nightly)
> Reporter: Milinda Lakmal Pathirage
> Attachments: svcskeltemplate.patch
>
>
> In the current implementation of generated code, when we execute the invoke method of the service skeleton it select the correct operation by getting the local name of the root xml element of the payload. But this case is only succeed when we use RPC style binding. Have to correct the operation selection logic by getting the operation name from the message context.
--
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-492) Wrong Logic inside generate service
skeleton's axis2_svc_skel__invoke function (WSDL2C Java
Version)
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462984 ]
Amila Chinthaka Suriarachchi commented on AXIS2C-492:
-----------------------------------------------------
patch applied thankx malinda
> Wrong Logic inside generate service skeleton's axis2_svc_skel_<Service Name>_invoke function (WSDL2C Java Version)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-492
> URL: https://issues.apache.org/jira/browse/AXIS2C-492
> Project: Axis2-C
> Issue Type: Bug
> Components: code generation
> Affects Versions: Current (Nightly)
> Reporter: Milinda Lakmal Pathirage
> Attachments: svcskeltemplate.patch
>
>
> In the current implementation of generated code, when we execute the invoke method of the service skeleton it select the correct operation by getting the local name of the root xml element of the payload. But this case is only succeed when we use RPC style binding. Have to correct the operation selection logic by getting the operation name from the message context.
--
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Resolved: (AXIS2C-492) Wrong Logic inside generate service
skeleton's axis2_svc_skel__invoke function (WSDL2C Java
Version)
Posted by "Dinesh Premalal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Premalal resolved AXIS2C-492.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
> Wrong Logic inside generate service skeleton's axis2_svc_skel_<Service Name>_invoke function (WSDL2C Java Version)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-492
> URL: https://issues.apache.org/jira/browse/AXIS2C-492
> Project: Axis2-C
> Issue Type: Bug
> Components: code generation
> Affects Versions: Current (Nightly)
> Reporter: Milinda Lakmal Pathirage
> Assigned To: Dinesh Premalal
> Fix For: 1.0.0
>
> Attachments: svcskeltemplate.patch
>
>
> In the current implementation of generated code, when we execute the invoke method of the service skeleton it select the correct operation by getting the local name of the root xml element of the payload. But this case is only succeed when we use RPC style binding. Have to correct the operation selection logic by getting the operation name from the message context.
--
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Assigned: (AXIS2C-492) Wrong Logic inside generate service
skeleton's axis2_svc_skel__invoke function (WSDL2C Java
Version)
Posted by "Dinesh Premalal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dinesh Premalal reassigned AXIS2C-492:
--------------------------------------
Assignee: Dinesh Premalal
> Wrong Logic inside generate service skeleton's axis2_svc_skel_<Service Name>_invoke function (WSDL2C Java Version)
> -------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-492
> URL: https://issues.apache.org/jira/browse/AXIS2C-492
> Project: Axis2-C
> Issue Type: Bug
> Components: code generation
> Affects Versions: Current (Nightly)
> Reporter: Milinda Lakmal Pathirage
> Assigned To: Dinesh Premalal
> Fix For: 1.0.0
>
> Attachments: svcskeltemplate.patch
>
>
> In the current implementation of generated code, when we execute the invoke method of the service skeleton it select the correct operation by getting the local name of the root xml element of the payload. But this case is only succeed when we use RPC style binding. Have to correct the operation selection logic by getting the operation name from the message context.
--
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org