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 "Eran Chinthaka (JIRA)" <ji...@apache.org> on 2005/11/23 04:16:36 UTC
[jira] Created: (AXIS2-307) Generated stubs do not consistent with Call
Generated stubs do not consistent with Call
-------------------------------------------
Key: AXIS2-307
URL: http://issues.apache.org/jira/browse/AXIS2-307
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: databinding
Reporter: Eran Chinthaka
Assigned to: Ajith Harshana Ranabahu
Fix For: 0.93
It seems that we do always have inconsistency with the methods in the Call API and the methods in the Stub. IMO, all the methods that are in Call should be made available via stub.
Current stub seems doesnot contain methods like setTimeOut. So shall we fix this ?
Plus, one solution for this recurring problem is to use properties to pass parameters via the Call api, so that there is no need to add methods whenever Call changes. I think its better to use the properties from here on.
But we need to fix the current 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
[jira] Resolved: (AXIS2-307) Generated stubs do not consistent with Call
Posted by "Eran Chinthaka (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-307?page=all ]
Eran Chinthaka resolved AXIS2-307:
----------------------------------
Resolution: Fixed
This is fixed with the introduction of Options to the MEPClients.
> Generated stubs do not consistent with Call
> -------------------------------------------
>
> Key: AXIS2-307
> URL: http://issues.apache.org/jira/browse/AXIS2-307
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: databinding
> Reporter: Eran Chinthaka
> Assignee: Ajith Harshana Ranabahu
> Fix For: 0.93
>
> It seems that we do always have inconsistency with the methods in the Call API and the methods in the Stub. IMO, all the methods that are in Call should be made available via stub.
> Current stub seems doesnot contain methods like setTimeOut. So shall we fix this ?
> Plus, one solution for this recurring problem is to use properties to pass parameters via the Call api, so that there is no need to add methods whenever Call changes. I think its better to use the properties from here on.
> But we need to fix the current 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
[jira] Commented: (AXIS2-307) Generated stubs do not consistent with Call
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-307?page=comments#action_12358328 ]
Davanum Srinivas commented on AXIS2-307:
----------------------------------------
more details here:
http://marc.theaimsgroup.com/?l=axis-dev&m=113271625424633&w=2
> Generated stubs do not consistent with Call
> -------------------------------------------
>
> Key: AXIS2-307
> URL: http://issues.apache.org/jira/browse/AXIS2-307
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: databinding
> Reporter: Eran Chinthaka
> Assignee: Ajith Harshana Ranabahu
> Fix For: 0.93
>
> It seems that we do always have inconsistency with the methods in the Call API and the methods in the Stub. IMO, all the methods that are in Call should be made available via stub.
> Current stub seems doesnot contain methods like setTimeOut. So shall we fix this ?
> Plus, one solution for this recurring problem is to use properties to pass parameters via the Call api, so that there is no need to add methods whenever Call changes. I think its better to use the properties from here on.
> But we need to fix the current 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