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 "Dushshantha Chandradasa (JIRA)" <ax...@ws.apache.org> on 2005/03/07 07:25:53 UTC
[jira] Created: (AXISCPP-508) Add server side test skeletons for all test WSDLs in CVS
Add server side test skeletons for all test WSDLs in CVS
---------------------------------------------------------
Key: AXISCPP-508
URL: http://issues.apache.org/jira/browse/AXISCPP-508
Project: Axis-C++
Type: Test
Environment: All
Reporter: Dushshantha Chandradasa
Attachments: ServiceSkeletons.zip
I have attached some server side test skeletons for the server side test automation
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
Re: Getting pointer exceptions on OS/400
Posted by Nadir Amra <am...@us.ibm.com>.
I think I have a solution with regards to recasting pointers to integers
and integers to pointers by just eliminating the recasting and taking the
object array as void** in files SoapDeserializer.cpp and ArrayBean.cpp.
Right now I do not get the pointer exceptions but I want to test it out a
little more.
Re: Getting pointer exceptions on OS/400
Posted by Nadir Amra <am...@us.ibm.com>.
Just to point to the code that I am worried about, here are the
ccurrences:
./soap/SoapDeSerializer.cpp: ptrval = reinterpret_cast < unsigned
long >(Array.m_Array);
./soap/SoapDeSerializer.cpp: reinterpret_cast < void
*>(ptrval + nIndex * itemsize);
./soap/SoapDeSerializer.cpp: ptrval = reinterpret_cast < unsigned
long >(Array.m_Array);
./soap/SoapDeSerializer.cpp: reinterpret_cast <
./common/ArrayBean.cpp: unsigned long ptrval =
reinterpret_cast<unsigned long>(m_value.cta->pObject);
./common/ArrayBean.cpp: pItem =
reinterpret_cast<void*>(ptrval+x*itemsize);
./common/ArrayBean.cpp: pItem =
reinterpret_cast<void*>(ptrval+x*itemsize);
which seems to be casting a pointer to an integer and then recasting it.
Can we rewrite that to not do that? What would be the proper code to do
that?
And are there any other occurrences that I need to worry about?
Nadir Amra/Rochester/IBM@IBMUS wrote on 04/10/2005 01:49:15 AM:
> I am trying to run the client tests, and half of the tests are
successful.
> As I look at some of the failures that are occurring, I see stuff like
>
> ==> Pointer not set for location referenced.
>
> I examined one of the failing test cases, the
> src\ws-axis\c\tests\auto_build\testcases\tests\ComplexLists.xml
testcase.
> And I looked at the code that is generated, and am wondering the
> following:
>
> Does the code that is generated convert pointers to integers and
> vice-versa? If it does, I think this needs to change. Not sure why it
> does so but we cannot assume that on all platforms a pointer fits into
an
> integer (specially 64-bit machine), and it is bad practice for
portability
> given that on some platforms pointers are protected, and if you convert
it
> to some other data type, you can never retrieve the pointer back.
>
> Does the code perform object copies via memcpy instead of using copy
> constructors? Why the heck do we do that? Again, I am not sure if that
> is legit in the object-oriented world and I do not think it is a good
> practice to do so.
>
> If either case is true, can someone tell me what I would need to change?
> Any help would be greatly appreciated.
>
>
>
>
>
Getting pointer exceptions on OS/400
Posted by Nadir Amra <am...@us.ibm.com>.
I am trying to run the client tests, and half of the tests are successful.
As I look at some of the failures that are occurring, I see stuff like
==> Pointer not set for location referenced.
I examined one of the failing test cases, the
src\ws-axis\c\tests\auto_build\testcases\tests\ComplexLists.xml testcase.
And I looked at the code that is generated, and am wondering the
following:
Does the code that is generated convert pointers to integers and
vice-versa? If it does, I think this needs to change. Not sure why it
does so but we cannot assume that on all platforms a pointer fits into an
integer (specially 64-bit machine), and it is bad practice for portability
given that on some platforms pointers are protected, and if you convert it
to some other data type, you can never retrieve the pointer back.
Does the code perform object copies via memcpy instead of using copy
constructors? Why the heck do we do that? Again, I am not sure if that
is legit in the object-oriented world and I do not think it is a good
practice to do so.
If either case is true, can someone tell me what I would need to change?
Any help would be greatly appreciated.
[jira] Commented: (AXISCPP-508) Add server side test skeletons for all test WSDLs in CVS
Posted by "Chinthana Danapala (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-508?page=comments#action_61205 ]
Chinthana Danapala commented on AXISCPP-508:
--------------------------------------------
Below shows which server stub for which WSDL.
1.Calculator.wsdl------------------------------------Calculator.cpp
2.ComplexTypeAll.wsdl----------------------------CalculatorWrapper.cpp
3.ExceptionTest.wsdl-------------------------------MathOps.cpp
4.ExtensibilityQuery.wsdl-------------------------ExtensibilityQueryPortType.cpp
5.FaultMappingDoc.wsdl--------------------------MathOps.cpp
6.inquire_v2.wsdl
7.InteropTestRound1Doc.wsdl--------------------InteropTestPortType.cpp
8.ManyTypeRefRoot.wsdl-------------------------ManyTypeRefRoot.cpp
9.MathOpsDoc.wsdl-------------------------------MathOps.cpp
10.RpcHttpHeaderTest1.wsdl--------------------InteropTestPortType.cpp
11.RpcHttpHeaderTest3.wsdl--------------------InteropTestPortType.cpp
12.RpcHttpHeaderTest5.wsdl--------------------InteropTestPortType.cpp
13.RpcHttpHeaderTest8.wsdl--------------------InteropTestPortType.cpp
14.RpcSoapHeaderTest2.wsdl-------------------InteropTestPortType.cpp
15.RpcSoapHeaderTest4.wsdl--------------------InteropTestPortType.cpp
16.RpcSoapHeaderTest8.wsdl--------------------InteropTestPortType.cpp
17.RpcSoapHeaderTest10.wsdl-------------------InteropTestPortType.cpp
18.SimpleArrayDoc.wsdl--------------------------ArrayTestPortType.cpp
19.SimpleRefDoc.wsdl-----------------------------RefTestPortType.cpp
20.SimpleTypeInnerUnbounded.wsdl-----------SimpleTypeInnerUnboundedWS.cpp
21.TestTransportTimeout.wsdl-------------------Timeout.cpp
22.XSDAttribute.wsdl-----------------------------XSDAttribute.cpp
23CalculatorDoc.wsdl-----------------Calculator.cpp
24 Enumeration.wsdl-------------------EnumerationWS.cpp
25 ExceptionTestDoc.wsdl----------MathOps.cpp
26 FaultMapping.wsdl-----------------MathOps.cpp
27 FourLevelTestDoc.wsdl
28 InteropTestRound1.wsdl---------InteropTestPortType.cpp
29 LargeReturningString.wsdl------LargeReturningString.cpp
30 MathOps.wsdl-----------------------MathOps.cpp
31 RecurseTypes.wsdl---------------RecurseTypesWS.cpp
32 RpcHttpHeaderTest2.wsdl-----InteropTestPortType.cpp
33 RpcSoapHeaderTest3.wsdl--- InteropTestPortType.cpp
34 RpcHttpHeaderTest4.wsdl-----InteropTestPortType.cpp
35 RpcSoapHeaderTest6.wsdl--- InteropTestPortType.cpp
36 RpcHttpHeaderTest7.wsdl-----InteropTestPortType.cpp
37 RpcSoapHeaderTest1.wsdl---InteropTestPortType.cpp
38 RpcSoapHeaderTest9.wsdl---InteropTestPortType.cpp
39 SimpleArray.wsdl-----------------ArrayTestPortType.cpp
40 SimpleRef.wsdl--------------------RefTestPortType.cpp
41 SimpleTypeArray.wsdl--------- SimpleTypeArrayWS.cpp
42 SimpleTypeInnerUnboundedInOutput.wsdl------
SimpleTypeInnerUnboundedInOutputWS.cpp
> Add server side test skeletons for all test WSDLs in CVS
> --------------------------------------------------------
>
> Key: AXISCPP-508
> URL: http://issues.apache.org/jira/browse/AXISCPP-508
> Project: Axis-C++
> Type: Test
> Environment: All
> Reporter: Dushshantha Chandradasa
> Attachments: ServiceSkeletons.zip, server stub code.zip
>
> I have attached some server side test skeletons for the server side test automation
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXISCPP-508) Add server side test skeletons for all test WSDLs in CVS
Posted by "Chinthana Danapala (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-508?page=history ]
Chinthana Danapala updated AXISCPP-508:
---------------------------------------
Attachment: server stub code.zip
> Add server side test skeletons for all test WSDLs in CVS
> --------------------------------------------------------
>
> Key: AXISCPP-508
> URL: http://issues.apache.org/jira/browse/AXISCPP-508
> Project: Axis-C++
> Type: Test
> Environment: All
> Reporter: Dushshantha Chandradasa
> Attachments: ServiceSkeletons.zip, server stub code.zip
>
> I have attached some server side test skeletons for the server side test automation
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-508) Add server side test skeletons for all test WSDLs in CVS
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-508?page=history ]
Samisa Abeysinghe closed AXISCPP-508:
-------------------------------------
Resolution: Fixed
Fix Version: 1.5 Final
These are in CVS now. Thanks for the effort Dushshantha and Chinthana.
> Add server side test skeletons for all test WSDLs in CVS
> --------------------------------------------------------
>
> Key: AXISCPP-508
> URL: http://issues.apache.org/jira/browse/AXISCPP-508
> Project: Axis-C++
> Type: Test
> Environment: All
> Reporter: Dushshantha Chandradasa
> Fix For: 1.5 Final
> Attachments: ServiceSkeletons.zip, server stub code.zip
>
> I have attached some server side test skeletons for the server side test automation
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXISCPP-508) Add server side test skeletons for all test WSDLs in CVS
Posted by "Dushshantha Chandradasa (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-508?page=history ]
Dushshantha Chandradasa updated AXISCPP-508:
--------------------------------------------
Attachment: ServiceSkeletons.zip
> Add server side test skeletons for all test WSDLs in CVS
> --------------------------------------------------------
>
> Key: AXISCPP-508
> URL: http://issues.apache.org/jira/browse/AXISCPP-508
> Project: Axis-C++
> Type: Test
> Environment: All
> Reporter: Dushshantha Chandradasa
> Attachments: ServiceSkeletons.zip
>
> I have attached some server side test skeletons for the server side test automation
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira