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 "Franz Fehringer (JIRA)" <ax...@ws.apache.org> on 2006/01/03 16:33:00 UTC
[jira] Created: (AXISCPP-897) recent wsdl2ws generates wrong/inconsistent prototypes
recent wsdl2ws generates wrong/inconsistent prototypes
------------------------------------------------------
Key: AXISCPP-897
URL: http://issues.apache.org/jira/browse/AXISCPP-897
Project: Axis-C++
Type: Bug
Components: Client - Stub
Versions: 1.6 Alpha
Environment: W2KSP4 JDK 1.5.0_06
Reporter: Franz Fehringer
With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
More specifically, the input parameters are declared inconsistent, the output parameters consistent.
The header reads
void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
The source reads
void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
Second and more seriously the levels of indirection differ:
With
typedef xsd__int t_Expiry;
typedef xsd__string t_Language;
typedef xsd__int t_PositiveInt;
the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
There is also an issue with the output parameters:
OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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: (AXISCPP-897) recent wsdl2ws generates
wrong/inconsistent prototypes
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=all ]
Adrian Dick resolved AXISCPP-897:
---------------------------------
Fix Version: 1.6 Alpha
Resolution: Fixed
I have made some modifications to the WSDL2Ws tool so that it now correctly handles user-defined simple type restrictions.
I have tested this using the provided WSDL and the code now compiles and matches what I would expect based on the WSDL defintition, including:
- consistent type naming in prototype and implementation
- correct use of pointers for nillable/optional or if a string-based type for input and output parameters.
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Assignee: Adrian Dick
> Fix For: 1.6 Alpha
> Attachments: SessionManagementPortType.cpp, SessionManagementPortType.hpp, durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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] Updated: (AXISCPP-897) recent wsdl2ws generates wrong/inconsistent prototypes
Posted by "Franz Fehringer (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=all ]
Franz Fehringer updated AXISCPP-897:
------------------------------------
Attachment: durchstich.wsdl
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Attachments: durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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] Assigned: (AXISCPP-897) recent wsdl2ws generates
wrong/inconsistent prototypes
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=all ]
Adrian Dick reassigned AXISCPP-897:
-----------------------------------
Assign To: Adrian Dick
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Assignee: Adrian Dick
> Attachments: SessionManagementPortType.cpp, SessionManagementPortType.hpp, durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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: (AXISCPP-897) recent wsdl2ws generates
wrong/inconsistent prototypes
Posted by "Franz Fehringer (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=comments#action_12362527 ]
Franz Fehringer commented on AXISCPP-897:
-----------------------------------------
False alarm, bug still present.
I looked into the wrong subdirectory (AxisC 1.5 generated sources).
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Attachments: SessionManagementPortType.cpp, SessionManagementPortType.hpp, durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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: (AXISCPP-897) recent wsdl2ws generates
wrong/inconsistent prototypes
Posted by "Franz Fehringer (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=comments#action_12362202 ]
Franz Fehringer commented on AXISCPP-897:
-----------------------------------------
A short investigation reveals that two problems where introduced with recent changes:
The integer input parameters are now passed as pointers (perhaps for taking optional parameters into account).
The person who implemented this forgot to adapt header file generation accordingly.
For the output parameters one level of indirection (one star/asterisk) was added to the function definition in the source (.cpp).
As can be seen from the implementation afterwards this is wrong.
The declaration in the header file (same as in release 1.5) is correct.
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Attachments: SessionManagementPortType.cpp, SessionManagementPortType.hpp, durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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] Updated: (AXISCPP-897) recent wsdl2ws generates wrong/inconsistent prototypes
Posted by "Franz Fehringer (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=all ]
Franz Fehringer updated AXISCPP-897:
------------------------------------
Attachment: durchstich.xsd
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Attachments: durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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: (AXISCPP-897) recent wsdl2ws generates
wrong/inconsistent prototypes
Posted by "Franz Fehringer (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=comments#action_12362203 ]
Franz Fehringer commented on AXISCPP-897:
-----------------------------------------
Correction: the header file declaration is wrong too (one level of indirection too much).
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Attachments: SessionManagementPortType.cpp, SessionManagementPortType.hpp, durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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] Updated: (AXISCPP-897) recent wsdl2ws generates wrong/inconsistent prototypes
Posted by "Franz Fehringer (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=all ]
Franz Fehringer updated AXISCPP-897:
------------------------------------
Attachment: SessionManagementPortType.cpp
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Attachments: SessionManagementPortType.cpp, SessionManagementPortType.hpp, durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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] Closed: (AXISCPP-897) recent wsdl2ws generates
wrong/inconsistent prototypes
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=all ]
nadir amra closed AXISCPP-897.
------------------------------
Closing issue - reopen if there is still a problem.
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Issue Type: Bug
> Components: Client - Stub
> Affects Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Assigned To: Adrian Dick
> Fix For: 1.6 Alpha
>
> Attachments: durchstich.wsdl, durchstich.xsd, SessionManagementPortType.cpp, SessionManagementPortType.hpp
>
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXISCPP-897) recent wsdl2ws generates
wrong/inconsistent prototypes
Posted by "Franz Fehringer (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=comments#action_12362523 ]
Franz Fehringer commented on AXISCPP-897:
-----------------------------------------
This seems to be fixed in latest SVN, but i still wonder why given
<xsd:simpleType name="t_Expiry">
<xsd:restriction base="xsd:int">
<xsd:minInclusive value="4200"/>
<xsd:maxInclusive value="7200"/>
</xsd:restriction>
</xsd:simpleType>
resulting in
typedef xsd__int t_Expiry;
the header refers to t_Expiry and the source to xsd__int?
To my opinition this should be consistent (either both use _Expiry or both use xsd__int).
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Attachments: SessionManagementPortType.cpp, SessionManagementPortType.hpp, durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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] Updated: (AXISCPP-897) recent wsdl2ws generates wrong/inconsistent prototypes
Posted by "Franz Fehringer (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-897?page=all ]
Franz Fehringer updated AXISCPP-897:
------------------------------------
Attachment: SessionManagementPortType.hpp
> recent wsdl2ws generates wrong/inconsistent prototypes
> ------------------------------------------------------
>
> Key: AXISCPP-897
> URL: http://issues.apache.org/jira/browse/AXISCPP-897
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.6 Alpha
> Environment: W2KSP4 JDK 1.5.0_06
> Reporter: Franz Fehringer
> Attachments: SessionManagementPortType.cpp, SessionManagementPortType.hpp, durchstich.wsdl, durchstich.xsd
>
> With the latest SVN code i observe the following problem not present in the AxisC 1.5 release:
> Using the attached WSDL method prototypes differ between header (.hpp) and source (.cpp) (also attached to this mail).
> More specifically, the input parameters are declared inconsistent, the output parameters consistent.
> The header reads
> void Login(t_Expiry Value0, t_Language Value1, t_PositiveInt Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1);
> The source reads
> void SessionManagementPortType::Login(xsd__int* Value0, xsd__string Value1, xsd__int* Value2, t_Authentication* Value3, AXIS_OUT_PARAM t_Expiry ** OutValue0, AXIS_OUT_PARAM t_SessionToken ** OutValue1)
> First in the header file for the input parameters typedefed types (t_Expiry ...) are used but typedefed to types (xsd__int ...) in the source file (maybe a cosmetic glitch but nevertheless not desirable).
> Second and more seriously the levels of indirection differ:
> With
> typedef xsd__int t_Expiry;
> typedef xsd__string t_Language;
> typedef xsd__int t_PositiveInt;
> the first parameter Value0 (for example) is an integer in the header but a pointer in the source.
> There is also an issue with the output parameters:
> OutValue1 is a t_SessionToken** in current SVN but a t_SessionToken* in release 1.5.
--
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