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 Andrew Perry2 <PE...@uk.ibm.com> on 2004/08/16 17:42:33 UTC

Test service location




Most of the tests in the tests/auto_build/linux/testcases/client/cpp/
directory show a usage of "testname <server> <port> <other options...>",
but this usage is not reflected in the code and localhost and port 80 are
hardcoded. It would be useful if it could be implemented as we do not have
the services running on localhost or on port 80 so the test code must be
modified each time it is extracted from CVS.

Any objections if this gets implemented?

Regards

Andrew Perry
Clients for Web Service Stack
perryan@uk.ibm.com
Mail Point 102
IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
Tel. Internal 249828  External + 44 (0)1962 819828
Fax. + 44(0)1962 818080


RE: Test service location

Posted by Susantha Kumara <su...@opensource.lk>.
+1 
Please do it. 
What about having http://localhost:80/... to be default when user is not
giving an endpoint ?.

Susantha
---

> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
> Sent: Tuesday, August 17, 2004 7:41 AM
> To: Apache AXIS C Developers List
> Subject: Re: Test service location
> 
> It is a good idea to pass these options.
> 
> However, rather than using <server> <port> <other options...>
> it would be far more flexible to use
> <endpoint> <other options>
> 
> This is because in most of the cliets we get a statement of the form:
> sprintf(endpoint, "http://%s:%s/axis/base", server, port);
> 
> I often have to change this to
> sprintf(endpoint, "http://%s:%s/axis/services/echo", server, port);
> where I test my service against a Java service.
> (Note the difference in the location of the service)
> 
> Hence the most felxible way, in my openion, is to pass the endpoint as
a
> whole to the client. This
> would make sure that I do not have to edit any of the client code to
test
> a given client with
> different services. (Compile once, test with many)
> 
> Thanks,
> Samisa...
> 
> --- Andrew Perry2 <PE...@uk.ibm.com> wrote:
> 
> >
> >
> >
> >
> > Most of the tests in the
tests/auto_build/linux/testcases/client/cpp/
> > directory show a usage of "testname <server> <port> <other
options...>",
> > but this usage is not reflected in the code and localhost and port
80
> are
> > hardcoded. It would be useful if it could be implemented as we do
not
> have
> > the services running on localhost or on port 80 so the test code
must be
> > modified each time it is extracted from CVS.
> >
> > Any objections if this gets implemented?
> >
> > Regards
> >
> > Andrew Perry
> > Clients for Web Service Stack
> > perryan@uk.ibm.com
> > Mail Point 102
> > IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
> > Tel. Internal 249828  External + 44 (0)1962 819828
> > Fax. + 44(0)1962 818080
> >
> >
> 
> 
> 
> 
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> http://promotions.yahoo.com/new_mail


Re: Test service location

Posted by Samisa Abeysinghe <sa...@yahoo.com>.
It is a good idea to pass these options.

However, rather than using <server> <port> <other options...>
it would be far more flexible to use
<endpoint> <other options>

This is because in most of the cliets we get a statement of the form:
sprintf(endpoint, "http://%s:%s/axis/base", server, port);

I often have to change this to
sprintf(endpoint, "http://%s:%s/axis/services/echo", server, port);
where I test my service against a Java service.
(Note the difference in the location of the service)

Hence the most felxible way, in my openion, is to pass the endpoint as a whole to the client. This
would make sure that I do not have to edit any of the client code to test a given client with
different services. (Compile once, test with many)

Thanks,
Samisa...

--- Andrew Perry2 <PE...@uk.ibm.com> wrote:

> 
> 
> 
> 
> Most of the tests in the tests/auto_build/linux/testcases/client/cpp/
> directory show a usage of "testname <server> <port> <other options...>",
> but this usage is not reflected in the code and localhost and port 80 are
> hardcoded. It would be useful if it could be implemented as we do not have
> the services running on localhost or on port 80 so the test code must be
> modified each time it is extracted from CVS.
> 
> Any objections if this gets implemented?
> 
> Regards
> 
> Andrew Perry
> Clients for Web Service Stack
> perryan@uk.ibm.com
> Mail Point 102
> IBM UK Laboratories. Hursley Park, Winchester, Hants. SO21 2JN
> Tel. Internal 249828  External + 44 (0)1962 819828
> Fax. + 44(0)1962 818080
> 
> 



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