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 <PERRYAN@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
|