Weblogic Webservices Typemapping

Hi,

I am creating a webservice in Weblogic

public ResponseT price(RequestT request) {
.....
}

The ResponseT and RequestT objects are defined in an XSD. I am using xmlbean to generate these objects.

When I do a servicegen task,. I am getting the following error

weblogic.xml.schema.binding.BindingException: Invalid class received: interface com.qwest.xmlSchema.RequestT loaded from file<jarfile>!/com/xxx/xmlSchema/RequestT.class. All classes that will be serialized or deserialized must be non-interface, non-abstract classes that provide a public default constructor

1. I was searching for a while and got to know that I need to do typemapping. What is the ant target, parameters and the jar file to do the type mapping in WL 10.3?
2. If I need to use the target autotype, what is the jar file and the type def to us the target in WL 10.3?
3. Is thr any way to specifiy the XSDs directly in the wsdl file to avoid such problems??
4. If I use the jwsc task and annotations instead of servicegen, will it resolve the problem??

Thanks & Regards
Mukund

Hi Mukund,

Invalid class received: interface com.qwest.xmlSchema.RequestT loaded from file

What kind of java class RequestT is(interface/abstract/non-abstract class)? Can you paste the code here?

Hi,

It is an interface which has been generated by the XMLBean

Thanks & Regards
Mukund

package com.qwest.xmlSchema.bim;

public interface RequestT extends org.apache.xmlbeans.XmlObject
{
public static final org.apache.xmlbeans.SchemaType type = (org.apache.xmlbeans.SchemaType)schema.system.s8E213516CE9FEB5A56661DFF069B999C.TypeSystemHolder.typeSystem.resolveHandle("requestta99ctype");

java.lang.String getRequestId();

org.apache.xmlbeans.XmlString xgetRequestId();

boolean isSetRequestId();

void setRequestId(java.lang.String requestId);

void xsetRequestId(org.apache.xmlbeans.XmlString requestId);
void unsetRequestId();
........................

.................
}
}

Hi Mukund,
The object expected by the web services engine should be serializable one. Apparently, interface class is getting picked up. In you method "price" change the request and response types to implementing classes rather than interfaces.