With axis 1.4 running on a Linux server I'm having a problem getting a windows
soap client tester (actually a tool called Magoo client) to grab the WSDL
published by axis (not the original WSDL, the autopublished WSDL).
The client is complaining that base64Binary cannot be resolved. This is a
standard soap encoding type used by one of the operations I have provided.
In the original WSDL I defined this at the top as xmlns:soapenc:
<?xml version = '1.0' encoding = 'UTF-8' ?>
<wsdl:definitions
name="webapi"
targetNamespace="urn:com.acme.webapi"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:webapi="urn:com.acme.webapi"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; >
etc..
I then used ant task wsdl2java etc to generate stubs, deploy.wsdd etc and
deploy the service on the server.
However when I query http://server/axis/services/webapi?wsdl, it imports the
namespace but does not define a xmlns:soapenc:
<wsdl:definitions targetNamespace="urn:com.acme.webapi">
<wsdl:types>
<schema targetNamespace="urn:com.acme.webapi">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
I think this is causing the base64Binary resolution problem at the client,
because later in the published WSDL there are references to soapenc even
though it wasn't explicitly defined.
Any ideas?
--
-Paul McMahon
-01763 261 466 ext 569
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
