Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Automating server side test implimentation
Date: Mon, 7 Mar 2005 08:12:49 +0600
Message-ID: <403DD48EAE182940B89ECEAFE03F969002D16401@cs-mailsvr.Virtusa.com>
Thread-Topic: Automating server side test implimentation
Thread-Index: AcUguQdT0Zy5bc0+QP+5L89Bz3RUYwCAAN0w
From: "Samisa Abeysinghe" <SAbeysinghe@virtusa.com>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>

> So I am thinking of having a workaround for that. If the adminservice
and
> adminclient can be improved to do the above, deployment can also be
truly
> automated.

In case of ant based client test framework for each wsdl: it takes a
wsdl, generate source, copy prewritten main, compile client and run,
progress to next wsdl

In case of server side, I think we have to have a different strategy.
We may have to have server.wsdd pre-written.

Then what we can do is for each wsdl: take wsdl, generate server code,
copy impl code which is pre-written, compile the wsdl and go to next
wsdl.
After all wsdls are dealt with only, apache has to be run to host the
services. Then the client framework could be run against the services
hosted.

In other words, it is too cumbersome to get a WSDL, and test it for both
server side and client side testing at once. We have to keep the server
side and client side testing independent as there needs to be room for
testing only the client side with java services.

Thanks,
Samisa...

-----Original Message-----
From: sanjaya singharage [mailto:sanjayas@opensource.lk]=20
Sent: Friday, March 04, 2005 6:41 PM
To: Apache AXIS C Developers List
Subject: Re: Automating server side test implimentation

Hi all,
I myself have been working on automating building and deployment of the
serverside of the ant framework. So far I have been able to generate
code
and build the services using the same methods used in the client ant
scripts
(code reuse).
deployment though is going to be difficult to automate at this point.
The
existing adminservice and adminclients are not compiling (and I haven't
tried hard to fix them) and even if they worked, I  don't remember being
able to change wsdd values through the adminservice client. What I need
here
is to change the value of the classname parameter.

So I am thinking of having a workaround for that. If the adminservice
and
adminclient can be improved to do the above, deployment can also be
truly
automated.
I have not made any changes to the existing client side ant scripts.
However
the serverside script written is dependent on some of the initialization
stuff from the client side scripts.

sanjaya.

----- Original Message -----
From: "Andrew Perry2" <PERRYAN@uk.ibm.com>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Cc: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Sent: Friday, March 04, 2005 5:24 PM
Subject: RE: Automating server side test implimentation


> I have no objections to the changes being made, but this change will
break
> the old shell script based framework. If it is no longer used by
anyone
> then I agree that the duplicate WSDLs be removed.
>
> Does anyone use the non-Ant test framework?
>
> Non-response will be assumed as a not in use and the duplicate WSDLs
will
> be removed.
>
> Regards,
>
>
> Andrew Perry
> IBM Web Services Client for C/C++
> perryan@uk.ibm.com
> Mail Point 127
> IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
> Tel. Internal 249828  External + 44 (0)1962 819828
> Fax. + 44(0)1962 818080
>
>
>
>              "Samisa
>              Abeysinghe"
>              <SAbeysinghe@virt
To
>              usa.com>                  "Apache AXIS C Developers List"
>                                        <axis-c-dev@ws.apache.org>
>              04/03/2005 10:40
cc
>
>
Subject
>              Please respond to         RE: Automating server side test
>               "Apache AXIS C           implimentation
>              Developers List"
>
>
>
>
>
>
>
>
>
> Hi Andrew,
>              OK. Thank you for the info. I jumped into this wrong
> conclusion
> because the WSDL files were duplicated with the test name.
>
>              I think the best solution in this case would be to
removed
the
> duplicates and update ws-axis/c/auto_build/testcases/tests.
>              Should we wait till the upcoming changes are complete or
is
it
> OK if the duplicate WSDLs are changed now?
>
> Thanks,
> Samisa...
>
>
>
> -----Original Message-----
> From: Andrew Perry2 [mailto:PERRYAN@uk.ibm.com]
> Sent: Friday, March 04, 2005 4:22 PM
> To: Apache AXIS C Developers List
> Cc: Apache AXIS C Developers List
> Subject: RE: Automating server side test implimentation
>
> Hi Samisa,
>
> The Ant based framework does NOT use the WSDL name. The Ant based
> framework
> uses the Ant test properties files in the
> ws-axis/c/auto_build/testcases/tests directory. This is an XML
property
> file. One of the properties in this file is the WSDL name so many
tests
> can
> use the same WSDL, client code, expected output files if required.
>
> Please read the anttest-guide.html in the docs directory for more
> information on the Ant test framework.
>
> Regards,
>
> Andrew Perry
> IBM Web Services Client for C/C++
> perryan@uk.ibm.com
> Mail Point 127
> IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
> Tel. Internal 249828  External + 44 (0)1962 819828
> Fax. + 44(0)1962 818080
>
>
>
>
>              "Samisa
>
>              Abeysinghe"
>
>              <SAbeysinghe@virt
> To
>              usa.com>                  "Apache AXIS C Developers List"
>
>                                        <axis-c-dev@ws.apache.org>
>
>              04/03/2005 10:04
> cc
>
>
>
> Subject
>              Please respond to         RE: Automating server side test
>
>               "Apache AXIS C           implimentation
>
>              Developers List"
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Andrew,
>              Thank you for the prompt response.
>
>              Well it looks like too many changes if we change port
type.
> Hence I would not change it.
>
>              It would be great if we could get rid of the duplicate
> WSDLs
> in
> the test folder. But as the ant based auto test framework for client
> uses the WSDL name, I am not sure if it is possible.
>
>              BTW, script based tests are no more used as the scripts
are
> not
> up to date.
> Thanks,
> Samisa...
>
>
> -----Original Message-----
> From: Andrew Perry2 [mailto:PERRYAN@uk.ibm.com]
> Sent: Friday, March 04, 2005 3:40 PM
> To: axis-c-dev@ws.apache.org
> Cc: Apache AXIS C User List
> Subject: Re: Automating server side test implimentation
>
> The changing of the portType name in the WSDL will, as you want,
change
> the
> names of the generated stubs.
>
> This will effect the following files for each test using the changed
> service.
>
> 1) Test client code will need to be changed to use the new stub name
> 2) Expected request files may need to be changed if endpoint changes
> 3) Ant test properties files may need to change if endpoint changes
> 4) Ant test properties files may need to change for handler tests if
> soapAction is also updated in handler
>
> This will be a large change. Currently 41 tests are based around the
> CalculatorDoc wsdl
>
> 16 tests use the InteropTestRound1 WSDL, though there are 16 copies of
> it
> in the wsdls directory. If the Ant test framework is used then these
> duplicate WSDLs can be removed. Several other WSDLs can be replaced.
> MathOps.wsdl is almost identical to FaultMapping.wsdl which is the
same
> as
> ExceptionTest.wsdl. These 3 WSDLs can be replaced by 1. The same is
true
> for the Doc versions of the WSDLs. The MathOps test can either be
> removed
> or use the FaultMapping WSDL.
>
> If the script based test framework is no longer used then all these
> duplicate WSDLs can be removed/merged so there will only be 1 version
of
> a
> WSDL in the wsdls directory. I feel that this will be a much smaller
> change
> than renaming the portType in each of the effected WSDLs as only the
> WSDL
> name will need to be updated in the Ant test properties file. Is the
> script
> based test framework still used?
>
> Also more tests are coming soon so, some of them based on the existing
> WSDLs so I would prefer if any changes are made that the changes be
> delayed
> a few weeks.
>
> Regards,
>
> Andrew Perry
> IBM Web Services Client for C/C++
> perryan@uk.ibm.com
> Mail Point 127
> IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
> Tel. Internal 249828  External + 44 (0)1962 819828
> Fax. + 44(0)1962 818080
>
>
>
>
>              Samisa Abeysinghe
>
>              <samisa.abeysingh
>
>              e@gmail.com>
> To
>                                        Apache AXIS C User List
>
>              04/03/2005 04:23          <axis-c-user@ws.apache.org>
>
>
> cc
>
>
>              Please respond to
> Subject
>               "Apache AXIS C           Re: Automating server side test
>
>                 User List"             implimentation
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Simply put,
>
> If we change the PortType name in the test WSDL file, would that have
> an impact on the current ant based client test framework.
>
> We would like the PortType to be the same as the name of the WSDL
> file, so that we have unique names to the services in the test
> framerowk.
>
> Thanks,
> Samisa...
>
>
> On Fri, 4 Mar 2005 10:15:12 +0600, Chinthana C. Dinapala
> <CDinapala@virtusa.com> wrote:
> >
> >
> > Hi,
> >
> >
> >
> > We are trying to automated the server side to test case, which will
> help
> to
> > test client with the sever side.
> >
> > But we have problem here several test will generate same file in
auto
> > generated skeleton.
> >
> >
> >
> > E.g. MathOps.cpp use by FaultMapping.wsdl, FaultMappingDoc.wsdl,
> ect..
> >
> >
> >
> > IT is the same contents all in these files but, as in client we are
> > searching client file by WSDL file name.
> >
> > Here we can't search from WSDL file type if they have same name in
> file.
> >
> > We can rename port type and get the unique file name to each WSDL.
> >
> > But if clients use the server port types it will be problem.
> >
> >
> >
> > Does anyone have idea on this?
> >
> >
> >
> > Thanks
> >
> >
> >
> >
> >
> > Chinthana Dinapala
> >
> > Associate Software Engineer
> >
> > Virtusa Corp.
> > 16th Floor, West Tower
> > World Trade Center
> >
> > Colombo 01
> >
> >
> >
> >
> >
> > Creating competitive advantage
> >
> >
>
>
>
>
>
>
>