One problem with your WSDL is that two of the elements in your Con type reference a type (impl:ArrayOf_soapenc_string) that hasn't been defined:
<element name="products" nillable="true" type="impl:ArrayOf_soapenc_string"/> <element name="areas" nillable="true" type="impl:ArrayOf_soapenc_string"/> As a result, any operation that exchanges the Con type or the ArrayOfCon type won't work. You need to add a type definition for this type. (or add addition typeMapping definitions in the wsdd for your string arrays.) I assume that Axis generated a different namespace for the Con and ArrayOfCon types because of your custom type mapping. There's no problem with including an element called "con" within a complex type called "Con". It's generally a bad idea to use overloaded methods with SOAP. Each SOAP implementation handles them somewhat differently. Do you still have the WSDL definition that Workshop generated? I suggest you start your Axis project with the WSDL file rather than with your application code. I also suggest that you switch to document/literal rather than rpc/encoded, but from your last response, I gather that you're not interested in making any significant changes. Anne ________________________________________ From: Florian Theurich [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 12, 2004 5:10 PM To: [EMAIL PROTECTED] Subject: WSDD configuration problems Hi there, I posted a similar message last week, but I did not get any feedback. That’s why I’ traing again… I appended my WSDL to this email. Below you can find the entry within the server-config.wsdd for my service: <service name="ConService" provider="java:RPC"> <parameter name="allowedMethods" value="*" /> <parameter name="className" value="com.xcell.ConService" /> <beanMapping qname="ns:Con" xmlns:ns="someService" languageSpecificType="java:com.xcell.Con" /> <typeMapping qname="ns:ArrayOfCon" xmlns:ns="someService" type="java:com.xcell.Con[]" serializer="org.apache.axis.encoding.ser.ArraySerializerFactory" deserializer="org.apache.axis.encoding.ser.ArrayDeserializerFactory" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; /> </service> Now I have following questions: 1) Is there anything wrong concerning my approach in the WSDD? 2) Is it a problem to have a element named ‘con’ in a complex type named ‘Con’? 3) Why does my WDSL display the URL ‘http://xcell.com’ in following line of the WSDL?Configuration problems… <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; namespace="http://xcell.com"/> 4) Is it allowed to have overloaded operations for a web service as one of my service’s method is overloaded! 5) Why do I get following error message in BEA Workshop 8.1 when trying to create a Service Control based on the appended WSDL WARNING: sampleWSDL.wsdl Line 0, Col 0: Operation "getConInfo" cannot be called. WARNING: sampleWSDL.wsdl Line 0, Col 0: Operation "getConInfoByYearAndProduct" cannot be called. WARNING: sampleWSDL.wsdl Line 0, Col 0: Operation "getConInfoByYearAndArea" cannot be called. WARNING: sampleWSDL.wsdl Line 0, Col 0: Operation "getConInfoByArea" cannot be called. WARNING: sampleWSDL.wsdl Line 0, Col 0: Operation "getConInfoByProduct" cannot be called. WARNING: sampleWSDL.wsdl Line 53, Col 0: WSDL warning: Schema type null undefined. WARNING: sampleWSDL.wsdl Line 59, Col 0: WSDL warning: Schema type null undefined. WARNING: sampleWSDL.wsdl Line 99, Col 0: WSDL warning: Schema type null undefined. WARNING: sampleWSDL.wsdl Line 105, Col 0: WSDL warning: Schema type null undefined. WARNING: sampleWSDL.wsdl Line 111, Col 0: WSDL warning: Schema type null undefined. WARNING: sampleWSDL.wsdl Line 125, Col 0: WSDL warning: Schema type null undefined. WARNING: sampleWSDL.wsdl Line 139, Col 0: WSDL warning: Schema type null undefined. WARNING: sampleWSDL.wsdl Line 145, Col 0: WSDL warning: Schema type null undefined. Can anyone out there help me please? Thanks Florian
