Hello Scott,
Judging from the information you're giving us it sounds like a service
you're calling isn't there. One solution would be to stopping calling
it, another would be to check why it is not there at the location you
are calling it (is it deployed correctly, are you calling it in the
right way, etc.).
Regards,
Dies
Scott Goldstein wrote:
In Axis 1.2, every time the client makes a webservice call, a
ConfigurationException is generated - "ConfigurationException - No
service named X is available". Building the stack trace for this
exception is expensive and I'd like to remove it. However, the only
solution I've seen on the web and in mailing lists for this problem
is to ignore it. Is there a better answer? Is there something that
I can add to the client-config.wsdd file to avoid this exception?
Thanks.
Scott
