You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Patrick Kent <p....@f5.com> on 2007/03/07 23:21:03 UTC
Malformed WSDL when generating EchoAttachmentService with ?wsdl
Did anyone find a solution for this problem? I am seeing exactly the
same thing with the Axis 1.4 EchoAttachment sample, using Tomcat 5.5.17.
Changing the namespace as per this post
(http://marc.theaimsgroup.com/?l=axis-user
<http://marc.theaimsgroup.com/?l=axis-user&m=114964405009333&w=2>
&m=114964405009333&w=2) does not remedy the issue.
The service works just fine when called from the command-line using the
EchoAttachment client. However, the WSDL is malformed. There is no
definition for DataHandler. I cannot consume this WSDL with more robust
clients such as SOAPScope.
Patrick
> Hi,
>
>
>
> I am using AXIS 1.2 over Tomcat 5.5.9 appserver with jdk1.5.0_03. I
have
> deployed my web services in both Linux and Windows. I found the
problem
> in only linux.
>
>
>
> The problem that I am facing is that the ?wsdl feature of the Axis is
> not generating the wsdl:types section correctly.
>
>
>
> I have defined a dataHandler element as follows
>
>
>
> <typeMapping
>
>
> xmlns:apachesoap="http://xml.apache.org/xml-soap"
>
> qname="apachesoap:DataHandler"
>
>
> languageSpecificType="java:javax.activation.DataHandler"
>
>
>
deserializer="org.apache.axis.encoding.ser.JAFDataHandlerDeserializerFac
> tory"
>
>
>
serializer="org.apache.axis.encoding.ser.JAFDataHandlerSerializerFactory
> "
>
>
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
>
> />
>
>
>
> And also I have added the xmlns:apachesoap in the deployment tag of my
> deploy.wsdd
>
>
>
> My web service in the deploy.wsdd looks like this.
>
>
>
> <operation returnQName="uploadStatus"
>
> returnType="xsd:boolean"
>
> name="uploadMediaTitle"
>
>
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>
>
>
> <parameter name="name" type="xsd:string"/>
>
> <parameter name="description"
> type="xsd:string"/>
>
> <parameter name="mediaTitleMimeTypeCode"
> type="xsd:string"/>
>
> <parameter name="dataHandler"
> type="apachesoap:DataHandler" />
>
> </operation>
>
>
>
> The problem is that the ?wsdl that generates the wsdl for my service
> does not generate the correct wsdl:type. It some times have and some
> times does not have the type declaration in the generated wsdl because
> of which the stubs generation throws the following error.
>
>
>
> java.io.IOException: Type DataHandler is referenced but not defined.
>
> at
> org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol
>
> Table.java:663)
>
> at
> org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543
>
> )
>
> at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
>
> a:516)
>
> at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
>
> a:493)
>
> at
> org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360)
>
> at java.lang.Thread.run(Thread.java:534)
>
>
>
> Can some one tell me the reason for this?
>
>
>
> Can some body tell me is this not the correct group that could help me
> or that I have to send the mail to developers list also? I hope
somebody
> might have got the above problem.
>
>
>
> Thanks and regards
>
>
>
> Subir S
>
>