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 John Hawkins <HA...@uk.ibm.com> on 2005/07/05 21:36:50 UTC
unitTest in build process
Hi folks,
I've created a new target in build.xml called buildAndRunUnitTests. It
works OK for me but before I make it the default target can someone else
please try it out? Just call the build.xml file as you would normally but
call the target buildAndRunUnitTests. Your cmd line should look something
like ->
ant <your usual build.xml -D options if you use any> <-file build.xml>
buildAndRunUnitTests
When we're happy that it works with everyone's environment I'll make it
the default target.
I'd also like to make it stop the build if it fails to run the unit tests
correctly (if everyone agrees) - I don't see the point in having the unit
tests if they can fail and not stop the build.
cheers for now,
John.
Re: unitTest in build process
Posted by Adrian Dick <ad...@uk.ibm.com>.
Hi,
Hmmm ... why are so many people having problems with this?
There must be some problem with the manifest, such that it isn't always
generated properly -- or perhaps a bug in the java task on some versions of
ANT.
Anyway, as the first line seems to work for more people, perhaps we should
change it.
Adrian
_______________________________________
Adrian Dick (adrian.dick@uk.ibm.com)
Nadir Amra <am...@us.ibm.com> wrote on 08/07/2005 17:21:55:
> In buildTest.xml, we have the following lines:
>
> <!-- use the following java task if client stub
> generation fails -->
> <!-- <java classname="org.apache.axis.wsdl.wsdl2ws.
> WSDL2Ws" fork="true"> -->
> <java jar="${dir.wsdl2ws}/wsdl2ws.jar" fork="true">
>
> I am wondering whether making the default the the first line and
> commenting out the second line will break anyone?
>
> When I run the test bucket, I get errors, I have to use the commented-out
> line to get things to work. If that works for everyone, then I think it
> should be the default, no?
>
>
>
> John Hawkins <HA...@uk.ibm.com> wrote on 07/05/2005 02:36:50 PM:
>
> >
> > Hi folks,
> >
> > I've created a new target in build.xml called buildAndRunUnitTests.
> > It works OK for me but before I make it the default target can
> > someone else please try it out? Just call the build.xml file as you
> > would normally but call the target buildAndRunUnitTests. Your cmd
> > line should look something like ->
> >
> > ant <your usual build.xml -D options if you use any> <-file build.
> > xml> buildAndRunUnitTests
> >
> > When we're happy that it works with everyone's environment I'll make
> > it the default target.
> >
> > I'd also like to make it stop the build if it fails to run the unit
> > tests correctly (if everyone agrees) - I don't see the point in
> > having the unit tests if they can fail and not stop the build.
> >
> > cheers for now,
> > John.
Re: unitTest in build process
Posted by Nadir Amra <am...@us.ibm.com>.
In buildTest.xml, we have the following lines:
<!-- use the following java task if client stub generation
fails -->
<!-- <java
classname="org.apache.axis.wsdl.wsdl2ws.WSDL2Ws" fork="true"> -->
<java jar="${dir.wsdl2ws}/wsdl2ws.jar" fork="true">
I am wondering whether making the default the the first line and
commenting out the second line will break anyone?
When I run the test bucket, I get errors, I have to use the commented-out
line to get things to work. If that works for everyone, then I think it
should be the default, no?
John Hawkins <HA...@uk.ibm.com> wrote on 07/05/2005 02:36:50 PM:
>
> Hi folks,
>
> I've created a new target in build.xml called buildAndRunUnitTests.
> It works OK for me but before I make it the default target can
> someone else please try it out? Just call the build.xml file as you
> would normally but call the target buildAndRunUnitTests. Your cmd
> line should look something like ->
>
> ant <your usual build.xml -D options if you use any> <-file build.
> xml> buildAndRunUnitTests
>
> When we're happy that it works with everyone's environment I'll make
> it the default target.
>
> I'd also like to make it stop the build if it fails to run the unit
> tests correctly (if everyone agrees) - I don't see the point in
> having the unit tests if they can fail and not stop the build.
>
> cheers for now,
> John.
Re: Compile problems with generated code
Posted by John Hawkins <HA...@uk.ibm.com>.
Fred - this should be in the test bucket - can you work out why it's not
please (it might be because it doesn't work :-(
Nadir Amra <am...@us.ibm.com>
30/09/2005 22:09
Please respond to
"Apache AXIS C Developers List"
To
"Apache AXIS C Developers List" <ax...@ws.apache.org>
cc
Subject
Re: Compile problems with generated code
Thanks Fred. The directory path, if it helps, is
obj/test/generated/cpp/UnitTest_InteropTestRound1/InteropTestPortType.cpp.
I will also look into this further.
Nadir K. Amra
Fred Preston <PR...@uk.ibm.com> wrote on 09/30/2005 04:15:07 AM:
>
> Hi Nadir,
> This is not a test I'm familiar with. I will create the
> environment and get back to you...
>
> Regards,
>
> Fred Preston.
>
>
>
> Nadir Amra <am...@us.ibm.com>
> 30/09/2005 05:19
> Please respond to "Apache AXIS C Developers List"
>
>
> To: "Apache AXIS C Developers List"
<ax...@ws.apache.org>
> cc:
> Subject: Compile problems with generated code
>
>
>
>
>
> I am getting compile problems trying to compile the code that is
generated
> for tests/InteropTestRound1.xml
>
> The code that fails to compile is InteropTestPortType.cpp and failures
all
> have to do with lines that look like the following:
>
> xsd__string_Array RetArray = {NULL, 0};
>
> RetArray = (xsd__string_Array&)m_pCall->getBasicArray(XSD_STRING,
> "_return", 0);
>
> The error is: An rvalue of type "axiscpp::Axis_Array" cannot be
converted
> to "axiscpp::xsd__string_Array &".
>
> Any clues?
>
> Nadir K. Amra
>
Re: Compile problems with generated code
Posted by Nadir Amra <am...@us.ibm.com>.
Thanks Fred. The directory path, if it helps, is
obj/test/generated/cpp/UnitTest_InteropTestRound1/InteropTestPortType.cpp.
I will also look into this further.
Nadir K. Amra
Fred Preston <PR...@uk.ibm.com> wrote on 09/30/2005 04:15:07 AM:
>
> Hi Nadir,
> This is not a test I'm familiar with. I will create the
> environment and get back to you...
>
> Regards,
>
> Fred Preston.
>
>
>
> Nadir Amra <am...@us.ibm.com>
> 30/09/2005 05:19
> Please respond to "Apache AXIS C Developers List"
>
>
> To: "Apache AXIS C Developers List"
<ax...@ws.apache.org>
> cc:
> Subject: Compile problems with generated code
>
>
>
>
>
> I am getting compile problems trying to compile the code that is
generated
> for tests/InteropTestRound1.xml
>
> The code that fails to compile is InteropTestPortType.cpp and failures
all
> have to do with lines that look like the following:
>
> xsd__string_Array RetArray = {NULL, 0};
>
> RetArray = (xsd__string_Array&)m_pCall->getBasicArray(XSD_STRING,
> "_return", 0);
>
> The error is: An rvalue of type "axiscpp::Axis_Array" cannot be
converted
> to "axiscpp::xsd__string_Array &".
>
> Any clues?
>
> Nadir K. Amra
>
Re: Compile problems with generated code
Posted by Nadir Amra <am...@us.ibm.com>.
I am going to fix this by updating cpp/ClientStubHeaderWriter.java so that
the generated code will look like:
Axis_Array RetAxisArray = m_pCall->getBasicArray(XSD_STRING,
"_return", 0);
memcpy(&RetArray,&RetAxisArray,sizeof(Axis_Array));
which is what is done in other places in the code.
Nadir K. Amra
>
> Nadir Amra <am...@us.ibm.com>
> 30/09/2005 05:19
> Please respond to "Apache AXIS C Developers List"
>
> I am getting compile problems trying to compile the code that is
generated
> for tests/InteropTestRound1.xml
>
> The code that fails to compile is InteropTestPortType.cpp and failures
all
> have to do with lines that look like the following:
>
> xsd__string_Array RetArray = {NULL, 0};
>
> RetArray = (xsd__string_Array&)m_pCall->getBasicArray(XSD_STRING,
> "_return", 0);
>
> The error is: An rvalue of type "axiscpp::Axis_Array" cannot be
converted
> to "axiscpp::xsd__string_Array &".
>
> Any clues?
Re: Compile problems with generated code
Posted by Fred Preston <PR...@uk.ibm.com>.
Hi Nadir,
This is not a test I'm familiar with. I will create the
environment and get back to you...
Regards,
Fred Preston.
Nadir Amra <am...@us.ibm.com>
30/09/2005 05:19
Please respond to "Apache AXIS C Developers List"
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
cc:
Subject: Compile problems with generated code
I am getting compile problems trying to compile the code that is generated
for tests/InteropTestRound1.xml
The code that fails to compile is InteropTestPortType.cpp and failures all
have to do with lines that look like the following:
xsd__string_Array RetArray = {NULL, 0};
RetArray = (xsd__string_Array&)m_pCall->getBasicArray(XSD_STRING,
"_return", 0);
The error is: An rvalue of type "axiscpp::Axis_Array" cannot be converted
to "axiscpp::xsd__string_Array &".
Any clues?
Nadir K. Amra
Compile problems with generated code
Posted by Nadir Amra <am...@us.ibm.com>.
I am getting compile problems trying to compile the code that is generated
for tests/InteropTestRound1.xml
The code that fails to compile is InteropTestPortType.cpp and failures all
have to do with lines that look like the following:
xsd__string_Array RetArray = {NULL, 0};
RetArray = (xsd__string_Array&)m_pCall->getBasicArray(XSD_STRING,
"_return", 0);
The error is: An rvalue of type "axiscpp::Axis_Array" cannot be converted
to "axiscpp::xsd__string_Array &".
Any clues?
Nadir K. Amra