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 "Chinthana Danapala (JIRA)" <ax...@ws.apache.org> on 2005/03/29 11:36:17 UTC
[jira] Created: (AXISCPP-584) RpcHttpHeaderTest2 - Client Compilation - FAILED
RpcHttpHeaderTest2 - Client Compilation - FAILED
------------------------------------------------
Key: AXISCPP-584
URL: http://issues.apache.org/jira/browse/AXISCPP-584
Project: Axis-C++
Type: Bug
Components: Client - Stub
Versions: 1.5 Final
Reporter: Chinthana Danapala
It gives following error.
[cc] RpcHttpHeaderTest2Client.cpp
[cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTest2Clien
t.cpp(120) : error C2374: 'bSuccess' : redefinition; multiple initialization
[cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTe
st2Client.cpp(57) : see declaration of 'bSuccess'
[cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTest2Clien
t.cpp(121) : error C2374: 'iRetryIterationCount' : redefinition; multiple initia
lization
[cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTe
st2Client.cpp(58) : see declaration of 'iRetryIterationCount'
[cc] Generating Code...
[cc] cl failed with return code 2
callCompileLinkedClient:
compileClient:
validateClientCompilationIfBuilding:
[echo] RpcHttpHeaderTest2 - Client Compilation - FAILED
--
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: backing up customised ant configuration
Posted by sanjaya singharage <sa...@opensource.lk>.
Please see my comments below....
----- Original Message -----
From: "Adrian Dick" <ad...@uk.ibm.com>
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Sent: Tuesday, March 29, 2005 7:26 PM
Subject: Re: backing up customised ant configuration
> Hi,
>
> This all sounds good.
>
> I have few comments below on things that can be done for client-side
> testing which can help avoid this problem. I haven't (yet) tried the
> server-side testing, so am uncertain if it can do the same.
>
> Regards,
> Adrian
> _______________________________________
> Adrian Dick (adrian.dick@uk.ibm.com)
>
>
> "sanjaya singharage" <sa...@opensource.lk> wrote on 29/03/2005
13:38:19:
>
> > A small ant script backupconf.xml is now created so that testers can
> back-up
> > and restore locally modified ant configurations. The targets are backup
> and
> > restore.
> >
> > What is backed up is...
> > 1. the server.wsdd.PLATFORM for the ant service framework
> Are these not generated "on-the-fly" by the ant framework? As is done when
> testing client-side handlers.
>
No. because the server.wsdd requires the allowed methods to be declared
within a parameter element and I could not find a way to make them visible
to the ant scripts since it can only be known through the wsdl/wsdl2ws. I
tried to use the generated deploy.wsdd as a property file to obtain the
allowed method information but was unable because there are several elements
with the same name "parameter", but I think there might be a way to do it.
and so for the service framework we need to keep a static server.wsdd file
at least for the moment, which needs to be update whenever new service is
added.
> > 2. build.PLATFORM.properties
> An alternative is to use -Ddir.properties=<my dir with my version of
> build.PLATFORM.properties>
>
> > 3. The client side test XMLs
> You can specify -Dtest.list=<location my test.list file> which is simply a
> test file with an entry for each desired <test>.xml to be used, instead of
> having to delete those you're currently not interested in.
>
can this list specify a set of xmls in a separate location other than the
original location in cvs? My idea in backing these up were to allow a tester
to have his own endpoints rather than the default ones.
> > 4. The services XMLs
> Perhaps a similar system could be used here as in step 3.
>
>
>
Re: backing up customised ant configuration
Posted by John Hawkins <ha...@uk.ibm.com>.
+1 for using the current property based system where we can
Adrian Dick/UK/IBM@IBMGB
29/03/2005 14:26
Please respond to
"Apache AXIS C Developers List"
To
"Apache AXIS C Developers List" <ax...@ws.apache.org>
cc
Subject
Re: backing up customised ant configuration
Hi,
This all sounds good.
I have few comments below on things that can be done for client-side
testing which can help avoid this problem. I haven't (yet) tried the
server-side testing, so am uncertain if it can do the same.
Regards,
Adrian
_______________________________________
Adrian Dick (adrian.dick@uk.ibm.com)
"sanjaya singharage" <sa...@opensource.lk> wrote on 29/03/2005
13:38:19:
> A small ant script backupconf.xml is now created so that testers can
back-up
> and restore locally modified ant configurations. The targets are backup
and
> restore.
>
> What is backed up is...
> 1. the server.wsdd.PLATFORM for the ant service framework
Are these not generated "on-the-fly" by the ant framework? As is done when
testing client-side handlers.
> 2. build.PLATFORM.properties
An alternative is to use -Ddir.properties=<my dir with my version of
build.PLATFORM.properties>
> 3. The client side test XMLs
You can specify -Dtest.list=<location my test.list file> which is simply a
test file with an entry for each desired <test>.xml to be used, instead of
having to delete those you're currently not interested in.
> 4. The services XMLs
Perhaps a similar system could be used here as in step 3.
Re: backing up customised ant configuration
Posted by Adrian Dick <ad...@uk.ibm.com>.
Hi,
This all sounds good.
I have few comments below on things that can be done for client-side
testing which can help avoid this problem. I haven't (yet) tried the
server-side testing, so am uncertain if it can do the same.
Regards,
Adrian
_______________________________________
Adrian Dick (adrian.dick@uk.ibm.com)
"sanjaya singharage" <sa...@opensource.lk> wrote on 29/03/2005 13:38:19:
> A small ant script backupconf.xml is now created so that testers can
back-up
> and restore locally modified ant configurations. The targets are backup
and
> restore.
>
> What is backed up is...
> 1. the server.wsdd.PLATFORM for the ant service framework
Are these not generated "on-the-fly" by the ant framework? As is done when
testing client-side handlers.
> 2. build.PLATFORM.properties
An alternative is to use -Ddir.properties=<my dir with my version of
build.PLATFORM.properties>
> 3. The client side test XMLs
You can specify -Dtest.list=<location my test.list file> which is simply a
test file with an entry for each desired <test>.xml to be used, instead of
having to delete those you're currently not interested in.
> 4. The services XMLs
Perhaps a similar system could be used here as in step 3.
backing up customised ant configuration
Posted by sanjaya singharage <sa...@opensource.lk>.
A small ant script backupconf.xml is now created so that testers can back-up
and restore locally modified ant configurations. The targets are backup and
restore.
What is backed up is...
1. the server.wsdd.PLATFORM for the ant service framework
2. build.PLATFORM.properties
3. The client side test XMLs
4. The services XMLs
any thoughts?
sanjaya.
Re: GNU Make and VC++ projects for 1.5 release
Posted by John Hawkins <ha...@uk.ibm.com>.
My strong opinion is that we should stop trying to support systems we
evidently don't use!
The MS project files are a good thing to do because they are widely used
However, the GNU make system can be superceded by the ANT scripts. The ant
scripts are maintained by us at IBM on a daily basis.
Samisa Abeysinghe <sa...@virtusa.com>
29/03/2005 18:02
Please respond to
"Apache AXIS C Developers List"
To
Apache AXIS C Developers List <ax...@ws.apache.org>
cc
Subject
GNU Make and VC++ projects for 1.5 release
Hi All,
As I understand, the above are out of date.
Are we going to fix those before 1.5 release?
Thoughts please...
Thanks,
Samisa...
GNU Make and VC++ projects for 1.5 release
Posted by Samisa Abeysinghe <sa...@virtusa.com>.
Hi All,
As I understand, the above are out of date.
Are we going to fix those before 1.5 release?
Thoughts please...
Thanks,
Samisa...
[jira] Closed: (AXISCPP-584) RpcHttpHeaderTest2 - Client Compilation - FAILED
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-584?page=history ]
Samisa Abeysinghe closed AXISCPP-584:
-------------------------------------
Resolution: Fixed
Fix Version: 1.5 Final
Patch applied
> RpcHttpHeaderTest2 - Client Compilation - FAILED
> ------------------------------------------------
>
> Key: AXISCPP-584
> URL: http://issues.apache.org/jira/browse/AXISCPP-584
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.5 Final
> Reporter: Chinthana Danapala
> Assignee: Samisa Abeysinghe
> Fix For: 1.5 Final
>
> It gives following error.
> [cc] RpcHttpHeaderTest2Client.cpp
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTest2Clien
> t.cpp(120) : error C2374: 'bSuccess' : redefinition; multiple initialization
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTe
> st2Client.cpp(57) : see declaration of 'bSuccess'
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTest2Clien
> t.cpp(121) : error C2374: 'iRetryIterationCount' : redefinition; multiple initia
> lization
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTe
> st2Client.cpp(58) : see declaration of 'iRetryIterationCount'
> [cc] Generating Code...
> [cc] cl failed with return code 2
> callCompileLinkedClient:
> compileClient:
> validateClientCompilationIfBuilding:
> [echo] RpcHttpHeaderTest2 - Client Compilation - FAILED
--
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] Commented: (AXISCPP-584) RpcHttpHeaderTest2 - Client Compilation - FAILED
Posted by "Chinthana Danapala (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-584?page=comments#action_61724 ]
Chinthana Danapala commented on AXISCPP-584:
--------------------------------------------
I have done some modifications it's now compiling.
Index: RpcHttpHeaderTest2Client.cpp
===================================================================
RCS file: /home/cvspublic/ws-axis/c/tests/auto_build/testcases/client/cpp/RpcHtt
pHeaderTest2Client.cpp,v
retrieving revision 1.9
diff -u -r1.9 RpcHttpHeaderTest2Client.cpp
--- RpcHttpHeaderTest2Client.cpp 23 Mar 2005 15:45:06 -0000 1.9
+++ RpcHttpHeaderTest2Client.cpp 29 Mar 2005 09:37:25 -0000
@@ -117,8 +117,8 @@
ws.deleteTransportProperty("Date");
//now the request should not have these removed headers
- bool bSuccess = false;
- int iRetryIterationCount = 3;
+ bSuccess = false;
+ iRetryIterationCount = 3;
do
{
> RpcHttpHeaderTest2 - Client Compilation - FAILED
> ------------------------------------------------
>
> Key: AXISCPP-584
> URL: http://issues.apache.org/jira/browse/AXISCPP-584
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.5 Final
> Reporter: Chinthana Danapala
>
> It gives following error.
> [cc] RpcHttpHeaderTest2Client.cpp
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTest2Clien
> t.cpp(120) : error C2374: 'bSuccess' : redefinition; multiple initialization
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTe
> st2Client.cpp(57) : see declaration of 'bSuccess'
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTest2Clien
> t.cpp(121) : error C2374: 'iRetryIterationCount' : redefinition; multiple initia
> lization
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTe
> st2Client.cpp(58) : see declaration of 'iRetryIterationCount'
> [cc] Generating Code...
> [cc] cl failed with return code 2
> callCompileLinkedClient:
> compileClient:
> validateClientCompilationIfBuilding:
> [echo] RpcHttpHeaderTest2 - Client Compilation - FAILED
--
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] Assigned: (AXISCPP-584) RpcHttpHeaderTest2 - Client Compilation - FAILED
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-584?page=history ]
Samisa Abeysinghe reassigned AXISCPP-584:
-----------------------------------------
Assign To: Samisa Abeysinghe
> RpcHttpHeaderTest2 - Client Compilation - FAILED
> ------------------------------------------------
>
> Key: AXISCPP-584
> URL: http://issues.apache.org/jira/browse/AXISCPP-584
> Project: Axis-C++
> Type: Bug
> Components: Client - Stub
> Versions: 1.5 Final
> Reporter: Chinthana Danapala
> Assignee: Samisa Abeysinghe
> Fix For: 1.5 Final
>
> It gives following error.
> [cc] RpcHttpHeaderTest2Client.cpp
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTest2Clien
> t.cpp(120) : error C2374: 'bSuccess' : redefinition; multiple initialization
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTe
> st2Client.cpp(57) : see declaration of 'bSuccess'
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTest2Clien
> t.cpp(121) : error C2374: 'iRetryIterationCount' : redefinition; multiple initia
> lization
> [cc] C:\obj\test\generated\cpp\RpcHttpHeaderTest2\RpcHttpHeaderTe
> st2Client.cpp(58) : see declaration of 'iRetryIterationCount'
> [cc] Generating Code...
> [cc] cl failed with return code 2
> callCompileLinkedClient:
> compileClient:
> validateClientCompilationIfBuilding:
> [echo] RpcHttpHeaderTest2 - Client Compilation - FAILED
--
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