axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <samisa_abeysin...@yahoo.com>
Subject RE: Generated source in CVS
Date Tue, 31 Aug 2004 10:50:03 GMT

--- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:

> 
> 
> 
> 
> OK, I see what you're saying.
> 
> Hmm, not sure that this is going to work. As soon as we find a single test
> that we want to add we would then have a choice of either adding it into
> Axis-Java tests (and hence having to write a Java client) or adding it into
> C testsuite. This then turns into an "Axis" test-suite. Which is a good
> idea but not sure that we are ready to do this just yet?
> 
> Oh and - do they have the same level of automation in Axis-Java?
> 

This is a good point; and I am not sure of. May be we could use our own script.

Samisa...

> John Hawkins
> 
> 
> 
> 
>                                                                            
>              Samisa Abeysinghe                                             
>              <samisa_abeysingh                                             
>              e@yahoo.com>                                               To 
>                                        Apache AXIS C Developers List       
>              31/08/2004 10:58          <axis-c-dev@ws.apache.org>          
>                                                                         cc 
>                                                                            
>              Please respond to                                     Subject 
>               "Apache AXIS C           RE: Generated source in CVS         
>              Developers List"                                              
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>                                                                            
> 
> 
> 
> 
> Hi John,
>    Yes I agree that we have to implement the services in C for testing.
> 
>    Hence I agree to the fact that we need:
> 1. C clients for all tests.
> 2. C services for all tests
> 
> What I was proposing was that if we could align our tests to what we
> already have in Axis Java
> then we could use the Axis Java services for:
> 3. Java services for all tests.
> 
> However, if the test scope provided by existing Axis Java tests are not
> sufficient, then it makes
> sense to include code for Java services in our cvs.
> 
> Thanks,
> Samisa...
> 
> 
> --- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:
> 
> >
> >
> >
> >
> > Hi Samisa,
> >
> > I'm confused ! I'll repeat and see whether we can understand each other
> ->
> >
> > We need to have C at the server-side because this tests the Axis-C server
> -
> > right?
> > Therefore, using the Axis Java services will not test the Axis-C server -
> > right?
> > Therefore, whatever we do, if we want to test the C server  we need to
> > write C services - right?
> > Therefore if you are saying we use the Axis-Java services then we should
> > still right Axis-C services - right?
> >
> > We (Our group not the Axis community) would like to test against non-C
> > services too. This is effectively testing interoperability between a C
> > client and  a Java server - something that is good for the Axis C
> community
> > too. Therefore we would like to put all the test services code into CVS
> > (both C and Java). Thus we would have the following in the CVS tree ->
> >
> > C clients for all tests.
> > C services for all tests
> > Java services for all tests.
> >
> > Does this help explain my position?
> >
> > cheers,
> > John.
> >
> >
> >
> >
> >
> >
> 
> >              Samisa Abeysinghe
> 
> >              <samisa_abeysingh
> 
> >              e@yahoo.com>
> To
> >                                        Apache AXIS C Developers List
> 
> >              28/08/2004 03:23          <axis-c-dev@ws.apache.org>
> 
> >
> cc
> >
> 
> >              Please respond to
> Subject
> >               "Apache AXIS C           RE: Generated source in CVS
> 
> >              Developers List"
> 
> >
> 
> >
> 
> >
> 
> >
> 
> >
> 
> >
> >
> >
> >
> >
> > --- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:
> >
> > >
> > >
> > >
> > >
> > > Hi Damitha,
> > >
> > > OK, so we'll go ahead and put our test clients into the autobuild
> process
> > > then as this is independent of the running of the tests.
> > >
> > > re:
> > > >When we run a test it would be nice if the wsdl is downloaded into the
> > > >wsdl folder and generate stubs and then run the test. I guest being
> able
> > > >to download the wsdl implies that the web service is running?.
> > >
> > > Hmm, I think this is not a good idea as it would imply that the build
> had
> > > to be able to see the test suite - a bad dependency.
> > >
> > > I think we should work on the basis that the tests are built using the
> > > wsdl's in CVS and their associated clients are kept in CVS.
> > >
> > > We still have to work out a way to place the server side code into CVS
> in
> > > that case. This is going to invlove a directory structure for c and
> java
> > > services. What do you think - good idea?
> >
> > I proposed to use the same test cases as that of Axis Java to eliminate
> the
> > need of having Java
> > service code in our C++ cvs tree. Is that an acceptable solution? Or do
> we
> > need different services
> > to test againt, other than what is already available with Axis Java?
> >
> > Samisa...
> >
> >
> >
> > >
> > >
> > > John Hawkins
> > >
> > >
> > >
> > >
> > >
> >
> > >              damitha@opensourc
> >
> > >              e.lk
> >
> > >
> > To
> > >              27/08/2004 11:07          "Apache AXIS C Developers List"
> >
> > >                                        <axis-c-dev@ws.apache.org>
> >
> > >
> > cc
> 
=== message truncated ===



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

Mime
View raw message