Error serializing non-built in data type

Question

hi
I am getting the following exception while accessing a webservice which uses non-built-in
data types as parameter to the service method
Its called ProcessingOrderTO.
The ProcessingOrderTO has three sub-types.. one of which is a Collection
Does anybody encountred this before
I have also attch the WSDL generated .
I am using wls81 SP1
thanks
jas
java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SOAPException:
failed to serialize class mypackage.orderprocessing.processing.to.ProcessingOrderTOweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface java.util.Collection class context=TypedClassContext{schemaType=['java:language_builtins.util']:Collection};
nested exception is:
javax.xml.soap.SOAPException: failed to serialize class mypackage.orderprocessing.processing.to.ProcessingOrderTOweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface java.util.Collection class context=TypedClassContext{schemaType=['java:language_builtins.util']:Collection}
javax.xml.soap.SOAPException: failed to serialize class mypackage.orderprocessing.processing.to.ProcessingOrderTOweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface java.util.Collection class context=TypedClassContext{schemaType=['java:language_builtins.util']:Collection}
at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:328)
at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:297)
at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:619)
at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:206)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:444)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:430)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:270)
at mypackage.orderprocessing.processing.client.OrderProcessingAssemblerXDBeanPort_Stub.processOrder(OrderProcessingAssemblerXDBeanPort_Stub.java:45)
at mypackage.orderprocessing.processing.client.Client.main(Client.java:69)
[OrderProcessingAssemblerXDBean.wsdl]

Answer 1

Hi Mik
Thanks for these suggestions.I have now completely moved to specific types, instead
of the Collections and ArrayList.
Things seem to be working fine ....thanks for all your help
thanks
jas
"Michael Wooten" <[email protected]> wrote:
>
Hi Jas,
My mistake. I copied the code from a DII client and you are using a Stub
one :-)
The correct code is:
TypeMappingRegistry registry = service.getTypeMappingRegistry();
Where the service variable is what was returned from your XXX_Impl()
call.
You don't have to cast anything, because the object returned from that
method
already extends javax.xml.rpc.Service.
w.r.t. you "moreover" text:
As long as the definition of the non-built-in types is the same as the
WSDL you
sent earlier, you shouldn't have a problem. The question I have is why
are you
a using java.util.Collection object on a web service operation's method
signature,
in the first place? When you do this, you do to things:
1. Producing WSDL that has xsd:anyType for element types. xsd:anyTypes
are fine
for defining XML grammars (i.e. WSDL, SOAP, etc.), but they add too much
mystery
to a business service. They basically tell the WSDL consumer, "the content
of
this element can be anything, so you'll have to figure out what it is
when you
get it. Hee, hee, hee!"
2. Introducing Java-specific classes into your web service. If the extrasList
element always contains the same type of elements, the type for it should
be an
array of whatever that object is. If you used an ArrayList because you
don't know
how many elements this will be, you can still use it in the implementation,
and
call the toArray() method to return a typed array.
To me, it just seems wrong to use Java container objects (i.e. ArrayList,
Collection,
HashMap, Set, etc.) in a web service operation's method signature, because
it
goes against the "programming language agnostic" idea of web services
:-) Just
my two cents.
Regards,
Mike Wooten
"jas" <[email protected]> wrote:
hi Michael
thanks for the reply ..
I tried using the smippet below .. but instead got a ClassCast Exception
at
TypeMappingRegistry registry = ((Service) port).getTypeMappingRegistry();
Moreover
1. When i generate client-jars using the clientgen task, the definition
of my
non-built-in types is different ...
2.
thanks
jas
"Michael Wooten" <[email protected]> wrote:
Hi Jas,
From the stack trace, it looks like you are using a JAX-RPC stub client.
Our java.util.Collection
serializer/deserializer is assigned to the "java:language_builtins.util"
namespace,
so you'll need to register the ArrayList and Collection in the TypeMappingRegistry.
Here's a code snippet:
import java.util.ArrayList;
import java.util.Collection;
import javax.xml.soap.SOAPConstants;
import javax.xml.namespace.QName;
import javax.xml.rpc.Service;
import javax.xml.rpc.encoding.TypeMapping;
import javax.xml.rpc.encoding.TypeMappingRegistry;
import weblogic.xml.schema.binding.internal.builtin.JavaUtilArrayListCodec;
import weblogic.xml.schema.binding.internal.builtin.JavaUtilCollectionCodec;
TypeMappingRegistry registry = ((Service)port).getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(SOAPConstants.URI_NS_SOAP_ENCODING
mapping.register(
     ArrayList.class,
     new QName("java:language_builtins.util", "ArrayList"),
     new JavaUtilArrayListCodec(),
     new JavaUtilArrayListCodec()
mapping.register(
     Collection.class,
     new QName("java:language_builtins.util", "Collection"),
     new JavaUtilCollectionCodec(),
     new JavaUtilCollectionCodec()
//invoke the web service operation that uses the ArrayList and Collection
There use to be a problem were the type mapping information in the
MyServiceClient.jar
(the one that the clientgen Ant task produces), was incorrect, butI
think this
was fixed well before WLS 8.1 :-)
I haven't tested the above with WLS 8.1 SP 1, but I think it may fix
the problem
you are having.
BTW:
JavaUtilArrayListCodec and JavaUtilCollectionCodec are in ${WL_HOME}/server/lib/webserviceclient.jar.
Regards,
Mike Wooten
"jas" <[email protected]> wrote:
hi
I am getting the following exception while accessing a webservice
which
uses non-built-in
data types as parameter to the service method
Its called ProcessingOrderTO.
The ProcessingOrderTO has three sub-types.. one of which is a Collection
Does anybody encountred this before
I have also attch the WSDL generated .
I am using wls81 SP1
thanks
jas
java.rmi.RemoteException: web service invoke failed: javax.xml.soap.SOAPException:
failed to serialize class mypackage.orderprocessing.processing.to.ProcessingOrderTOweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface java.util.Collection classcontext=TypedClassContext{schemaType=['java:language_builtins.util']:Collection};
nested exception is:
javax.xml.soap.SOAPException: failed to serialize class mypackage.orderprocessing.processing.to.ProcessingOrderTOweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface java.util.Collection classcontext=TypedClassContext{schemaType=['java:language_builtins.util']:Collection}
javax.xml.soap.SOAPException: failed to serialize class mypackage.orderprocessing.processing.to.ProcessingOrderTOweblogic.xml.schema.binding.SerializationException:
mapping lookup failure. class=interface java.util.Collection classcontext=TypedClassContext{schemaType=['java:language_builtins.util']:Collection}
at weblogic.webservice.core.DefaultPart.invokeSerializer(DefaultPart.java:328)
at weblogic.webservice.core.DefaultPart.toXML(DefaultPart.java:297)
at weblogic.webservice.core.DefaultMessage.toXML(DefaultMessage.java:619)
at weblogic.webservice.core.ClientDispatcher.send(ClientDispatcher.java:206)
at weblogic.webservice.core.ClientDispatcher.dispatch(ClientDispatcher.java:143)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:444)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:430)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:270)
at mypackage.orderprocessing.processing.client.OrderProcessingAssemblerXDBeanPort_Stub.processOrder(OrderProcessingAssemblerXDBeanPort_Stub.java:45)
at mypackage.orderprocessing.processing.client.Client.main(Client.java:69)