axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Perry2 <PERR...@uk.ibm.com>
Subject Re: Test structure
Date Fri, 03 Sep 2004 12:40:20 GMT





>
> A question:
> > My position is that we should just stick with what we've got and write
> both
> > Java and C services for them.
>
> Would these Java services run with only Axis Java or support multiple
Java
> engines?
> >> The Java services we have here run against WAS5.02 and WAS 5.1 - the
> issue here is that WAS versions change the stuff they put into the EAR
> files so I think we can build a "generic" EAR file with the services in
> them and each application server can add any other information it needs.
> Andrew Perry has lots of experience in this area so what do you think
> Andrew?


I'm looking into what the generics are, and creating an Ant script to build
the actual services with the app server specific wsdl2java tool.


>
> A suggestion:
> > Any one else got any opinions? Otherwise I'm going to create a Java and
C
> > service structure asap.
>
> We currently have C++ services in samples/server/ and tests/server/
> folders.
> May be you add C++ services to those and create 'java' sub folders in
those
> for Java.
>
> >> Sounds fine to me but aren't these actually Server-side tests?
>
> Guys who have more experiance with server side please comment.
>
> Thanks,
> Samisa...
>
> --- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:
>
> >
> >
> >
> >
> > Hi Folks,
> >
> > we still have not worked out the tests and where the services are going
> to
> > be placed. I waant both Java and C services because lots of people are
> > using Java server-side.
> >
> > Samisa's position is that we write C clients for the Axis-Java tests.
> > (Samisa, correct me if I'm wrong here :-)
> >
> > However, this would mean that if we would be creating a "Axis" test
suite
> > and therefore if we wanted to add any more tests into the suite (more
> than
> > likely) then we would have to start adding them to the Axis-Java suite
> and
> > thus have to write Java clients for them. This is not something that
I'm
> > willing to do today for sure.
> >
> > My position is that we should just stick with what we've got and write
> both
> > Java and C services for them. Whether we supply a way to package the
> > services up is still up for debate (not in the first instance is my
> > opinion). However, the key point is that we need to put the services
into
> > CVS so that others can run the suite.
> >
> > Any one else got any opinions? Otherwise I'm going to create a Java and
C
> > service structure asap.
> >
> > thanks,
> > John.
> >
> >
> >
> >
> > John Hawkins
> >
> >
> >
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
>
>


Mime
View raw message