1) targetService problem unrelated to base64 encoding 2) Apparently Axis CAN handle base64 encoded parameters sent from .NET clients where JAX-RPC fails.
> -----Original Message----- > From: Rick Busch > Sent: Tuesday, October 29, 2002 7:16 PM > To: '[EMAIL PROTECTED]' > Subject: Can't find target service ... > > 1) I am trying to call an Axis service using a .NET client and am getting > the following error: > > System.Web.Services.Protocols.SoapException: The AXIS engine could not > find a target service to invoke! targetService is CertificationPortIF > at > System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClie > ntMessage message, WebResponse response, Stream responseStream) > > I'm sure the target URL of the .NET client proxy is correct. Any ideas? > > 2) Don't know if this is related, but ... > this error only began occurring after changing the Axis interface to > accept base64encoded parameters from the dot net client > We know there's a bug in JAX-RPC regarding dotnet clients and > base64encoding. > > Can Axis handle base64encoded parameters from .NET clients? > >
