Serialization error: no serializer is registered for class BasicDynaBean

Hi,
I have created webservice for the java class i have written. And i was also successful in deploying the webservice on the application server.
when i was trying to test the webservice, few of the operations were working fine. But i came across such kind of error message when i am trying to invoke one of the methods i have written . Below is the following error message seen from SOAP respone, highlighted with bold.
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://dataaccess/types/" xmlns:ns1="http://www.oracle.com/webservices/internal/literal"><env:Body><env:Fault><faultcode>env:Server</faultcode>
<faultstring>Internal Server Error (serialization error: no serializer is registered for (class org.apache.commons.beanutils.BasicDynaBean, null))</faultstring></env:Fault></env:Body></env:Envelope>
I am using RowSetDynaClass for representing the results of an SQL query.
Please let me know if any one could provide me a solution for this error.
Thanks.

Similar Messages

I'm getting this error message: "User not registered for online use" when i'm trying to download music/ track names from a CD into ITunes on my Windows 8 PC. I'm registered and my itunes account/ appleID are all correct and working.

I'm getting this error message: "User not registered for online use" when i'm trying to download music/ track names from a CD into ITunes on my Windows 8 PC. I'm registered and my itunes account/ appleID are all correct and working.

The ""not recognized for on-line use". error is associated with the Gracenote service that iTunes uses to look up and retrieve metadata for CDs. Some users have reported that this error occurs when trying to import from CD, subsequent to upgrading to version 12. A number of slightly different solutions have been reported (though all of a similar nature).
Try walking through the following steps - before starting you may have to enable hidden files and folders to be viewed - in Windows 7 / Windows Explorer select Organize > Folder and search options, then on the View tab make sure that Show hidden files, folders and drives is selected. Without this you won't see the AppData folder in C:\Users\username\
Exit iTunes
In Windows Explorer, go to the folder C:\Users\username\AppData\Roaming\Apple Computer\iTunes
Delete the following files:
CD Info.cidb
com.apple.iTunes.Gracenote.plist
Restart iTunes
Insert a CD and see if details are now correctly retrieved from Gracenote
If this doesn't work:
In iTunes, select Edit > Preferences and make a note (or take a screenshot) of your preferences settings in all relevant tabs
Exit iTunes
In Windows Explorer, go to the folder C:\Users\username\AppData\Roaming\Apple Computer\iTunes
Delete the following file:iTunesPrefs.xml
Restart iTunes
Insert a CD and see if details are now correctly retrieved from Gracenote
If this second procedure does work, you'll need to restore other iTunes preferences settings to those that you noted in step 1.
If this one didn't work:
Exit iTunes
Check the following folders:
C:\Users\username\AppData\Local\Apple Computer\iTunes
C:\Users\username\AppData\LocalLow\Apple Computer\iTunes
Delete any copies of the following files:
CD Info.cidb
com.apple.iTunes.Gracenote.plist
iTunesPrefs.xml
Restart iTunes
Insert a CD and see if details are now correctly retrieved from Gracenote
Again, if this procedure does work, you'll need to restore other iTunes preferences settings to those that you noted in step 1 of the second procedure. If you're still not able to retrieve CD info:
Exit iTunes
In Windows, select Start > Control Panel > Programs and Features. Find the entry for iTunes, right-click and select Repair.
When this process has finished, restart iTunes
Insert a CD and see if details are now correctly retrieved from Gracenote
If none of these have worked (and almost everything I've seen suggests you should be OK by this point), you may have an issue with the installation and configuration of iTunes itself. If you have got this far, see turingtest2's notes on Troubleshooting issues with iTunes for Windows updates for advice on how to remove and replace of all components of iTunes.

How to register for class while using ActiveX

Hi
I am trying to use ActiveX to send an email with Microsoft Outlook. I have found an example Vi. but i was getting an error with code "-2147221164" (Class not registered in Outlook_Mail-1.vi). How to register for that class and what are the files required for that registration.
Attachments:
Outlook_Mail-1.vi ‏31 KB

Here is a picture of the Photosmart eStation:
Don't forgot to say thanks by giving "Kudos" if I helped solve your problem.
When a solution is found please mark the post that solves your issue.
Every problem has a solution!

Compiler error type of object in for (Class obj : Items) - why?

Hi all,
I'm new to Java generics and am in the process of converting some
legacy code. I have encountered a particular error which I do not
understand the reason for, since I think the compiler has enough
information about the code to work out type information. The following
code shows a test class which demonstrates this error:
import java.util.Collection;
public class Test
    interface Base {}
    static class Impl1 implements Base{}
    public <T extends Base> Collection<T> getCollection(Class<? extends Base> cls)
        return null;
    void someMethod()
        for ( Impl1 obj : getCollection( Impl1.class ))
            // *** compiler complains about the line above ***
            // compiler says:
            // Test.java:22: incompatible types
            // found   : Test.Base
            // required: Test.Impl1
            //        for ( Impl1 obj : getCollection( Impl1.class ))
            //                                        ^
    void someMethod2()
        Collection<Impl1> coln = getCollection(Impl1.class);
        for (Impl1 obj : coln)
            // do something here with obj
}Why should the compiler complain where it does ( the line marked with
asterisks) in someMethod, but does not reject the declaration statement
in someMethod2? I would have assumed both are the same and the
compiler has the same type information at its disposal to determine
the correct type.
Cheers,
Bonny

The Java 5 compiler not only looks at a method's name and arguments, but also at its return value in order to determine whether a method is callable and what type should be infered for its type parameters.
In your example the type parameter T is only used in the declaration of the method's return type. Note that there is no relation between T and the type of the argument cls!
Thus, the compiles needs to know what type of variable the return value will be assigned to.
Hence, someMethod2 can be resolved, whereas in someMethod there is no assignment of the return value. (Rather, an implicit call to Iterable.iterator()).
You can solve this problem by forming a relation between the method's argument, its return type and its type parameter. Just declare the method like this:
public <T extends Base> Collection<T> getCollection(Class<T> cls)
        return null;
    }

Serialization error while invoking a Java web service

Hi,
I've a requirement where I need to create a Java web service, which returns a collection (a set of records).
The way I've created a web service is by having a Java Class, which internally calls a Pl/sql package returning Ref cursors and a bean Class, which wraps the method of the Java Class, to return the collection. I could create the web service successfully and could invoke the end point. The end point looks like this: http://localhost:8988/MyJavaWebService-New_JWS-context-root/MyWebService_finalSoapHttpPort
The method exposed for the web service in my Java class is of type ArrayList, to fetch the collection element.
After giving the input at the end point, while I say invoke, for the web service, I get the following error:
<env:Envelope
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:ns0="http://mypkg/types/"
xmlns:ns1="http://www.oracle.com/webservices/internal/literal">
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Internal Server Error (serialization error: no serializer is registered for (class mypkg.EmpBean, null))</faultstring>
</env:Fault>
</env:Body>
</env:Envelope>
I've tried making my exposed method of type Vector as well and re-generated the web service. But still I face the same issue at invocation.
Can anybody help me out and hint me on how I should proceed? I'm not sure if my approach is correct and so please correct me if I'm wrong.
Thanks in Advance,
Gayathri

Hi,
do you use 10.1.2 or 10.1.3?
Take a look at:
Re: How to create a web service with ArrayList or Collection

Java.rmi.ServerException: Internal Server Error (serialization error....)

Hi to all.
I have two classes.
The first is:
public class FatherBean implements Serializable {
public String name;
public int id;
/** Creates a new instance of ChildBean */
public FatherBean() {
this.name= null;
this.id = 0;
public String getName() {
return name;
public void setName(String name) {
this.name = name;
public int getId() {
return id;
public void setId(int id) {
this.id = id;
The second is :
public class ChildBean extends FatherBean implements Serializable {
public double number;
/** Creates a new instance of ChildBean */
public ChildBean() {
super();
this.number = 0.0;
public double getNumber() {
return number;
public void setNumber(double number) {
this.number = number;
A test client class implements the following method that is exposed as web service:
public java.util.Collection getBeans() {
java.util.Collection beans = new ArrayList();
ChildBean childBean1 = new ChildBean();
ChildBean childBean2 = new ChildBean();
childBean1.setId(100);
childBean1.setName("pippo");
childBean1.setNumber(3.9);
childBean2.setId(100000);
childBean2.setName("pluto");
childBean2.setNumber(4.7);
beans.add(childBean1);
beans.add(childBean2);
return beans;
When I invoke the web service to url:
http://localhost:8080/Prova
and invoke the correspondent method on jsp client, throws exception:
java.rmi.ServerException: Internal Server Error (serialization error: no serializer is registered for (class test.ChildBean, null))
     at com.sun.xml.rpc.client.StreamingSender._raiseFault(StreamingSender.java:357)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:228)
     at ws.ProvaClientGenClient.ProvaRPC_Stub.getBeans(ProvaRPC_Stub.java:59)
     at ws.ProvaClientGenClient.getBeans_handler.doAfterBody(getBeans_handler.java:64)
     at jasper.getBeans_TAGLIB_jsp._jspService(_getBeans_TAGLIB_jsp.java:121)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.iplanet.ias.web.jsp.JspServlet$JspServletWrapper.service(JspServlet.java:552)
     at com.iplanet.ias.web.jsp.JspServlet.serviceJspFile(JspServlet.java:368)
     at com.iplanet.ias.web.jsp.JspServlet.service(JspServlet.java:287)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
     at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
     at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
     at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)
Where is the problem? Will be ChildBean that extends FatherBean? Wich settings on Sun Java Studio Enterprise 6 2004Q1?
Thank you.

Hi,
This forum is for Sun Java Studio Creator related questions. Could you pls post your message in the appropriate forum.
Thank you
Cheers :-)

Web services with JDeveloper - serialization error

Dear all,
I have an issue with web services created with JDeveloper 10.1.3.2.0.
Namely, this is what I do:
1. I've created some TopLink classes from tables; one of this classes is called Task (and it's located in a package called "integration")
2. I've created another class, called Integration, where I use these TopLink classes; in this new class I have a method called getTasksStatus, which returns an ArrayList containing Task objects
3. I've created a web service from this class (Integration) by right-clicking on the class name in Applications Navigator and choosing Create J2EE Web Service.
When I call the method getTasksStatus from the test web service (endpoint),
I get this error:
Oct 8, 2007 7:14:30 PM oracle.webservices.service
SEVERE: serialization error: no serializer is registered for (class integration.Task, null) serialization error: no serializer is registered for (class integration.Task, null)
When I call a method which returns a primitive type, everything is fine.
I understand the problem, but I don't know a solution yet. Could you please help ?
Thank you,
Best regards,
Sorin

One solution to this problem is to make sure that the complex type you are using in yous service interface do implement the JAVA Bean as per the spec (at least Oracle's interpretation of it).
You need to have getter/setter for all members and you need to have an empty ctor() to create new instances of your objects. In some cases, the design time let you get by, but the runtime fails in the code generation.
In your case, the 'Task' class may have some issue.
Hope it helps,
-eric

Serialization error when calling web service method

Hi,
In JDeveloper 10.1.3.1, I'm working on an EJB that will be deployed as a web service. There is a method in the EJB that is defined to return a generic Object, but in the implementation, it really returns one of several possible specialized bean objects. I can deploy the EJB successfully to IAS 10.1.3.1.
I created a web service proxy from the wsdl that was generated from deploying the EJB. Using the proxy, I try to call the EJB method and cast the method's return value to the bean object I know should be returned. However, I get an error like this:
java.rmi.ServerException:
start fault message:
Internal Server Error (serialization error: no serializer is registered for (class com.test.TestBean, null))
:end fault message
Does anyone know how this serialization error can be resolved? If I change the web service method signature to return the bean object that is actually being returned (instead of Object), then it works fine. But I want to be able to define the method to return a generic Object because I plan to make the method flexible enough to return several different types of bean objects. Whenever the client calls the method, it will know what is the actual object being returned and I had planned to cast the return value to its actual class.
Thanks for any ideas.

Well, I think so... I've followed all the steps, and my merged WSDL file seems like the one in page 12...
Any suggestion, please?
Thank you,

Serialization error while returning Value Object from Web Service

Hi
I have developed a sample Web Service (RPC based), it returns Customer Value Object
when client calls getCustomer method.
I have written a Client (attached the client source code) to invoke the web service
when the client invokes the Web Service it throws an Exception , the Exception
Exception in thread "main" serialization error: no serializer is registered for
(null, {java:customer}Customer)
at com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer(DynamicInternalTypeMappingRegistry.java:62)
at com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPResponseSerializer.java:72)
at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(ReferenceableSerializerImpl.java:47)
at com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCall.java:382)
at com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.java:364)
at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
at ClientwithWSDL.main(ClientwithWSDL.java:63)
CAUSE:
no serializer is registered for (null, {java:customer}Customer)
at com.sun.xml.rpc.encoding.TypeMappingUtil.getSerializer(TypeMappingUtil.java:41)
at com.sun.xml.rpc.encoding.InternalTypeMappingRegistryImpl.getSerializer(InternalTypeMappingRegistryImpl.java:287)
at com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer(DynamicInternalTypeMappingRegistry.java:47)
at com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPResponseSerializer.java:72)
at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(ReferenceableSerializerImpl.java:47)
at com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCall.java:382)
at com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.java:364)
at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
at ClientwithWSDL.main(ClientwithWSDL.java:63)
If someone can help me to fix the issue, it will be great.
Thanks
Jeyakumar Raman.

I guess, this is because the RI client is not finding the
codec to ser/deser your Value Object. You need to register
the codec in the type mapping registry before you invoke
the web service method.
Here is a sample:
Service service = factory.createService( serviceName );
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping mapping = registry.getTypeMapping(
SOAPConstants.URI_NS_SOAP_ENCODING );
mapping.register( SOAPStruct.class,
new QName( "http://soapinterop.org/xsd", "SOAPStruct" ),
new SOAPStructCodec(),
new SOAPStructCodec() );
BTW, you can do the same exact thing on the client by using
WLS impl of JAX-RPC. Is there a reason for using RI on the
client side?
regards,
-manoj
"Jeyakumar Raman" <[email protected]> wrote in message news:[email protected]...
Hi Manoj,
Thanks for your information, Yes, my client is Sun's JAX-RPC based, but the Server
Implementation is done using Weblogic 7.0. When I invoke the Client without WSDL.
It works fine without any problem. But when I invoke the webservice using WSDL,
I am getting this problem.
Here is my Client Code :
* This class demonstrates a java client invoking a WebService.
import java.net.URL;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.Service;
import javax.xml.rpc.Call;
import javax.xml.rpc.ParameterMode;
import javax.xml.namespace.QName;
import customer.Customer;
public class ClientwithWSDL {
private static String qnameService = "CustomerService";
private static String qnamePort = "CustomerServicePort";
private static String BODY_NAMESPACE_VALUE =
"http://jeyakumar_3957:7001/Customer";
private static String ENCODING_STYLE_PROPERTY =
"javax.xml.rpc.encodingstyle.namespace.uri";
private static String NS_XSD =
"http://www.w3.org/2001/XMLSchema";
private static String URI_ENCODING =
"http://schemas.xmlsoap.org/soap/encoding/";
private static String method="getCustomer";
private static String endpoint="http://jeyakumar_3957:7001/webservice/CustomerService?WSDL";
public static void main(String[] args) throws Exception {
// create service factory
ServiceFactory factory = ServiceFactory.newInstance();
// define qnames
QName serviceName =new QName(BODY_NAMESPACE_VALUE, qnameService);
QName portName = new QName(BODY_NAMESPACE_VALUE, qnamePort);
QName operationName = new QName("",method);
URL wsdlLocation = new URL(endpoint);
// create service
Service service = factory.createService(wsdlLocation, serviceName);
// create call
Call call = service.createCall(portName, operationName);
// invoke the remote web service
Customer result = (Customer) call.invoke(new Object[0]);
System.out.println("\n");
System.out.println(result);
"manoj cheenath" <[email protected]> wrote:
>
>
>Hi Jayakumar,
>
>From the stack trace it looks like you are using sun's
>RI of JAX-RPC. I am not sure what is going wrong with RI.
>
>WLS 7.0 got its own implementation of JAX-RPC. Check
>out the link below for details:
>
>http://edocs.bea.com/wls/docs70/webserv/index.html
>
>
>Let us know if you need more details.
>
>--=20
>
>regards,
>-manoj
>
>
>
> "Jeyakumar" <[email protected]> wrote in message =
>news:[email protected]...
>
> Hi
>
> I have developed a sample Web Service (RPC based), it returns Customer
>=
>Value Object
> when client calls getCustomer method.
>
> I have written a Client (attached the client source code) to invoke
>=
>the web service
> when the client invokes the Web Service it throws an Exception , the
>=
>Exception
>
>
> Exception in thread "main" serialization error: no serializer is =
>registered for
> (null, {java:customer}Customer)
> at =
>com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer=
>(DynamicInternalTypeMappingRegistry.java:62)
>
> at =
>com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPRespo=
>nseSerializer.java:72)
> at =
>com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(Reference=
>ableSerializerImpl.java:47)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCal=
>l.java:382)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.ja=
>va:364)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
> at ClientwithWSDL.main(ClientwithWSDL.java:63)
>
> CAUSE:
>
> no serializer is registered for (null, {java:customer}Customer)
> at =
>com.sun.xml.rpc.encoding.TypeMappingUtil.getSerializer(TypeMappingUtil.ja=
>va:41)
> at =
>com.sun.xml.rpc.encoding.InternalTypeMappingRegistryImpl.getSerializer(In=
>ternalTypeMappingRegistryImpl.java:287)
> at =
>com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer=
>(DynamicInternalTypeMappingRegistry.java:47)
>
> at =
>com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPRespo=
>nseSerializer.java:72)
> at =
>com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(Reference=
>ableSerializerImpl.java:47)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCal=
>l.java:382)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.ja=
>va:364)
> at =
>com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
> at ClientwithWSDL.main(ClientwithWSDL.java:63)
>
> If someone can help me to fix the issue, it will be great.
>
> Thanks
> Jeyakumar Raman.
>
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
><HTML><HEAD>
><META http-equiv=3DContent-Type content=3D"text/html; =
>charset=3Diso-8859-1">
><META content=3D"MSHTML 6.00.2713.1100" name=3DGENERATOR>
><STYLE></STYLE>
></HEAD>
><BODY bgColor=3D#ffffff>
><DIV><FONT face=3DCourier size=3D2>Hi Jayakumar,</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2>From the stack trace it looks like
>=
>you are using=20
>sun's</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2>RI of JAX-RPC. I am not sure
>=
>what is going=20
>wrong with RI.</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2>WLS 7.0 got its own implementation
>of =
>
></FONT><FONT face=3DCourier size=3D2>JAX-RPC. Check</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2>out the link below for =
>details:</FONT></DIV>
><DIV><FONT face=3DCourier size=3D2></FONT><FONT face=3DCourier=20
>size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2><A=20
>href=3D"http://edocs.bea.com/wls/docs70/webserv/index.html">http://edocs.=
>bea.com/wls/docs70/webserv/index.html</A></FONT></DIV>
><DIV><FONT face=3DCourier size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2></FONT> </DIV>
><DIV><FONT face=3DCourier size=3D2>Let us know if you need more=20
>details.</FONT></DIV>
><DIV><BR>-- <BR><BR>regards,<BR>-manoj</DIV>
><DIV> </DIV>
><DIV><BR> </DIV>
><BLOCKQUOTE=20
>style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
>BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
> <DIV>"Jeyakumar" <<A=20
> href=3D"mailto:[email protected]">[email protected]</A>>
>=
>wrote in=20
> message <A=20
> =
>href=3D"news:[email protected]">news:[email protected]=
>a.com</A>...</DIV><BR>Hi<BR><BR>I=20
> have developed a sample Web Service (RPC based), it returns Customer
>=
>Value=20
> Object<BR>when client calls getCustomer method.<BR><BR>I have written
>=
>a Client=20
> (attached the client source code) to invoke the web service<BR>when
>=
>the client=20
> invokes the Web Service it throws an Exception , the=20
> Exception<BR><BR><BR>Exception in thread "main" serialization error:
>=
>no=20
> serializer is registered for<BR>(null,=20
> {java:customer}Customer)<BR>
>=
>at=20
> =
>com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer=
>(DynamicInternalTypeMappingRegistry.java:62)<BR><BR> &nb=
>sp; =20
> at=20
> =
>com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPRespo=
>nseSerializer.java:72)<BR> =20
> at=20
> =
>com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(Reference=
>ableSerializerImpl.java:47)<BR> =
>=20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCal=
>l.java:382)<BR> =20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.ja=
>va:364)<BR> =20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)<BR> =
> =20
> at ClientwithWSDL.main(ClientwithWSDL.java:63)<BR><BR>CAUSE:<BR><BR>no
>=
>
> serializer is registered for (null,=20
> {java:customer}Customer)<BR>
>=
>at=20
> =
>com.sun.xml.rpc.encoding.TypeMappingUtil.getSerializer(TypeMappingUtil.ja=
>va:41)<BR> =20
> at=20
> =
>com.sun.xml.rpc.encoding.InternalTypeMappingRegistryImpl.getSerializer(In=
>ternalTypeMappingRegistryImpl.java:287)<BR> =
> =20
> at=20
> =
>com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerializer=
>(DynamicInternalTypeMappingRegistry.java:47)<BR><BR> &nb=
>sp; =20
> at=20
> =
>com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPRespo=
>nseSerializer.java:72)<BR> =20
> at=20
> =
>com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(Reference=
>ableSerializerImpl.java:47)<BR> =
>=20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(BasicCal=
>l.java:382)<BR> =20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCall.ja=
>va:364)<BR> =20
> at=20
> =
>com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)<BR> =
> =20
> at ClientwithWSDL.main(ClientwithWSDL.java:63)<BR><BR>If someone can
>=
>help me=20
> to fix the issue, it will be great.<BR><BR>Thanks<BR>Jeyakumar=20
>Raman.</BLOCKQUOTE></BODY></HTML>
>
>
[att1.html]

Serialization error with WS session bean

Hi,
I'm running into a serious problem here at my project and I cannot find out what is going wrong.
I've made a scaled down version of the project I'm working on. This project gives the exact same error as in the main project.
I've created some simple POJO's with the model that should be returned by the session bean.
When I add some random test data and test the webservice I get the following error.
<faultstring>Internal Server Error ( serialization error : no serializer is registered for ( class nl.mk.test.canonicalmodel.ListObject, null )) </faultstring>
The model I use looks like this :
MainObject --> ListArrayObject --> ListObject
The implementation of these files.
package nl.mk.test.canonicalmodel;
import java.io.Serializable;
public class MainObject implements Serializable{
public MainObject() {
public String identification;
public ListArrayObject somelist;
package nl.mk.test.canonicalmodel;
import java.io.Serializable;
import java.util.List;
public class ListArrayObject implements Serializable{
public ListArrayObject() {
public String someId;
public List<ListObject> someList;
package nl.mk.test.canonicalmodel;
import java.io.Serializable;
public class ListObject implements Serializable {
public ListObject() {
public ListObject(String ident, String testfield1,
String testfield2, String testfield3
this.ident = ident;
this.testfield1 = testfield1;
this.testfield2 = testfield2;
this.testfield3 = testfield2;
public String ident;
public String testfield1;
public String testfield2;
public String testfield3;
The testWSBean that I've written looks like this.
package testws;
import java.util.ArrayList;
import java.util.List;
import javax.ejb.Stateless;
import javax.persistence.EntityManager;
import nl.mk.test.canonicalmodel.ListArrayObject;
import nl.mk.test.canonicalmodel.ListObject;
import nl.mk.test.canonicalmodel.MainObject;
import org.apache.log4j.Logger;
@Stateless(name="TestWSBean")
public class TestWSBeanBean implements TestWSBean, TestWSBeanLocal,
TestWSBeanWebService {
private EntityManager em;
* Private logging instance
private static final Logger log = Logger.getLogger(TestWSBean.class);
public TestWSBeanBean() {
public MainObject GeefWaarde(String testWaarde) {
MainObject result = new MainObject();
long fStart;
fStart = System.currentTimeMillis();
try {
log.debug("----------------------------");
result.identification = testWaarde;
ListArrayObject listarray = new ListArrayObject();
listarray.someId = "ABCDEF";
List<ListObject> listObj = new ArrayList<ListObject>();
ListObject listType1 = new ListObject();
listType1.testfield1 = "A";
listType1.testfield2 = "B";
listType1.testfield3 = "C";
listObj.add( listType1 );
ListObject listType2 = new ListObject();
listType2.testfield1 = "D";
listType2.testfield2 = "E";
listType2.testfield3 = "F";
listObj.add ( listType2);
listarray.someList = listObj;
result.somelist = listarray;
catch (Exception e) {
log.error(e.getMessage());
e.printStackTrace();
} finally {
log.debug("Ready to return results");
long fEnd;
fEnd = System.currentTimeMillis();
log.debug("time in ms : " + (fEnd - fStart));
return result;
Does anyone know why this testproject gives a Serializable error?
Thanks in advance

Issue with the classes generated on fly for internal use. Make sure all the related files you are using are compiled on the same version of weblogic which you are using(though not mandate).
Compile and bind the application again, and before redeploying the application, clear cache and temp.
Hope this helps.
Jeets.

Serialization error:Help

i felt completely lost in using JAXRPC.Zero documentation makes me to struggles a lot.Thanks for all forum users who is answering and resolving issues.
When i try to pass an array in webservice following error occurs>
serialization error: no serializer is registered for (null, {http://www.w3.org/2
001/XMLSchema}ArrayOfstring)
at com.sun.xml.rpc.encoding.DynamicInternalTypeMappingRegistry.getSerial
izer(DynamicInternalTypeMappingRegistry.java:62)
at com.sun.xml.rpc.encoding.soap.SOAPResponseSerializer.initialize(SOAPR
esponseSerializer.java:72)
at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.initialize(Refer
enceableSerializerImpl.java:47)
at com.sun.xml.rpc.client.dii.BasicCall.createRpcResponseSerializer(Basi
cCall.java:382)
at com.sun.xml.rpc.client.dii.BasicCall.getResponseDeserializer(BasicCal
l.java:364)
at com.sun.xml.rpc.client.dii.BasicCall.invoke(BasicCall.java:259)
WSDL file is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloWorld" targetNamespace="http://simplebean-hello.org/wsdl" xmlns:tns="http://simplebean-hello.org/wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ns2="http://simplebean-hello.org/types" xmlns:ns3="http://java.sun.com/jax-rpc-ri/internal">
<types>
<schema targetNamespace="http://simplebean-hello.org/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://simplebean-hello.org/types" xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<import namespace="http://java.sun.com/jax-rpc-ri/internal"/>
<complexType name="SimpleAccountBean">
<sequence>
<element name="balance" type="decimal"/>
<element name="customerName" type="string"/></sequence></complexType>
<complexType name="ArrayOfstring">
<complexContent>
<restriction base="soap-enc:Array">
<attribute ref="soap-enc:arrayType" wsdl:arrayType="string[]"/></restriction></complexContent></complexType></schema>
<schema targetNamespace="http://java.sun.com/jax-rpc-ri/internal" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://java.sun.com/jax-rpc-ri/internal" xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
<import namespace="http://simplebean-hello.org/types"/>
<complexType name="vector">
<complexContent>
<extension base="tns:list">
<sequence/></extension></complexContent></complexType>
<complexType name="list">
<complexContent>
<extension base="tns:collection">
<sequence/></extension></complexContent></complexType>
<complexType name="collection">
<complexContent>
<restriction base="soap-enc:Array">
<attribute ref="soap-enc:arrayType" wsdl:arrayType="anyType[]"/></restriction></complexContent></complexType></schema></types>
<message name="HelloIF_calculateInterest">
<part name="SimpleAccountBean_1" type="ns2:SimpleAccountBean"/></message>
<message name="HelloIF_calculateInterestResponse">
<part name="result" type="xsd:decimal"/></message>
<message name="HelloIF_reverse">
<part name="arrayOfString_1" type="ns2:ArrayOfstring"/></message>
<message name="HelloIF_reverseResponse">
<part name="result" type="ns2:ArrayOfstring"/></message>
<message name="HelloIF_sayHello">
<part name="Vector_1" type="ns3:vector"/></message>
<message name="HelloIF_sayHelloResponse">
<part name="result" type="ns3:vector"/></message>
<message name="HelloIF_sayHelloString">
<part name="String_1" type="xsd:string"/></message>
<message name="HelloIF_sayHelloStringResponse">
<part name="result" type="xsd:string"/></message>
<portType name="HelloIF">
<operation name="calculateInterest" parameterOrder="SimpleAccountBean_1">
<input message="tns:HelloIF_calculateInterest"/>
<output message="tns:HelloIF_calculateInterestResponse"/></operation>
<operation name="reverse" parameterOrder="arrayOfString_1">
<input message="tns:HelloIF_reverse"/>
<output message="tns:HelloIF_reverseResponse"/></operation>
<operation name="sayHello" parameterOrder="Vector_1">
<input message="tns:HelloIF_sayHello"/>
<output message="tns:HelloIF_sayHelloResponse"/></operation>
<operation name="sayHelloString" parameterOrder="String_1">
<input message="tns:HelloIF_sayHelloString"/>
<output message="tns:HelloIF_sayHelloStringResponse"/></operation></portType>
<binding name="HelloIFBinding" type="tns:HelloIF">
<operation name="calculateInterest">
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://simplebean-hello.org/wsdl"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://simplebean-hello.org/wsdl"/></output>
<soap:operation soapAction=""/></operation>
<operation name="reverse">
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://simplebean-hello.org/wsdl"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://simplebean-hello.org/wsdl"/></output>
<soap:operation soapAction=""/></operation>
<operation name="sayHello">
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://simplebean-hello.org/wsdl"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://simplebean-hello.org/wsdl"/></output>
<soap:operation soapAction=""/></operation>
<operation name="sayHelloString">
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://simplebean-hello.org/wsdl"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://simplebean-hello.org/wsdl"/></output>
<soap:operation soapAction=""/></operation>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/></binding>
<service name="HelloWorld">
<port name="HelloIFPort" binding="tns:HelloIFBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
client code is as follows:
package simplebean;
import java.util.*;
import javax.xml.rpc.Call;
import javax.xml.rpc.Service;
import javax.xml.rpc.JAXRPCException;
//import javax.xml.rpc.namespace.QName;
import javax.xml.rpc.ServiceFactory;
import javax.xml.rpc.ParameterMode;
import javax.xml.rpc.encoding.XMLType;
import javax.xml.namespace.*;
public class HelloClient2 {
private static String qnameService = "HelloWorld";
private static String qnamePort = "HelloIFPort";
private static String BODY_NAMESPACE_VALUE =
"http://simplebean-hello.org/wsdl";
private static String ENCODING_STYLE_PROPERTY =
"javax.xml.rpc.encodingstyle.namespace.uri";
private static String NS_XSD =
"http://www.w3.org/2001/XMLSchema";
private static String URI_ENCODING =
"http://schemas.xmlsoap.org/soap/encoding/";
public static void main(String[] args) {
try {
String endpoint= args[0];
ServiceFactory factory =
ServiceFactory.newInstance();
Service service =
factory.createService(new QName(qnameService));
               System.out.println("awrwe");
QName port = new QName(qnamePort);
Call call = service.createCall();
call.setPortTypeName(port);
call.setTargetEndpointAddress(endpoint);
call.setProperty(Call.SOAPACTION_USE_PROPERTY,
new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
QName QNAME_TYPE_STRING = new QName(NS_XSD,"ArrayOfstring");
               call.setReturnType(QNAME_TYPE_STRING);
call.setOperationName(new QName(BODY_NAMESPACE_VALUE,
"reverse"));
call.addParameter("arrayOfString_1", QNAME_TYPE_STRING,ParameterMode.IN);
String par[] = {"Hello"};
Object[] params = new Object[1];
params[0] = par;
String[] v1 = (String[])call.invoke(params);
               System.out.println(v1);
} catch (Exception ex) {
ex.printStackTrace();
What should i do to solve this problem?

CombinedSerializer nameSerializer = new Name_SOAPSerializer(nameQname, ENCODE_TYPE, NULLABLE, SOAPC
nameSerializer = new ReferenceableSerializerImpl(SERIALIZE_AS_REF, nameSerializer);
SerializerFactory nameSerializerFactory = new SingletonSerializerFactory(nameSerializer);
DeserializerFactory nameDeserializerFactory = new SingletonDeserializerFactory(nameSerializer);
CombinedSerializer nameArraySerializer = new ObjectArraySerializer(nameArrayTypeQname, ENCODE_TYPE,
ts.URI_ENCODING, nameArrayElementQname, nameQname, Name.class, 1, null);
nameArraySerializer = new ReferenceableSerializerImpl(SERIALIZE_AS_REF, nameArraySerializer);
SingletonSerializerFactory nameArraySerializerFactory = new SingletonSerializerFactory(nameArraySer
SingletonDeserializerFactory nameArrayDeserializerFactory = new SingletonDeserializerFactory(nameAr
CombinedSerializer innerSerializer = new Outer_Inner_SOAPSerializer(innerTypeQname, ENCODE_TYPE, NU
URI_ENCODING);
innerSerializer = new ReferenceableSerializerImpl(SERIALIZE_AS_REF, innerSerializer);
SerializerFactory innerSerializerFactory = new SingletonSerializerFactory(innerSerializer);
DeserializerFactory innerDeserializerFactory = new SingletonDeserializerFactory(innerSerializer);
CombinedSerializer indexedNamesSerializer = new IndexedNames_SOAPSerializer(indexedPropertyBeanType
ENCODE_TYPE, NULLABLE, SOAPConstants.URI_ENCODING);
indexedNamesSerializer = new ReferenceableSerializerImpl(SERIALIZE_AS_REF, indexedNamesSerializer);
SerializerFactory indexedNamesSerializerFactory = new SingletonSerializerFactory(indexedNamesSerial
DeserializerFactory indexedNamesDeserializerFactory = new SingletonDeserializerFactory(indexedNames
Service service = factory.createService(new QName(HELLO_SERVICE));
QName port = new QName(WSDL_NAMESPACE_VALUE, HELLO_PORT);
registerHelloHandlers(service, port);
TypeMappingRegistry registry = service.getTypeMappingRegistry();
TypeMapping typeMapping = registry.getTypeMapping(SOAPConstants.URI_ENCODING);
typeMapping.register(Name.class, nameQname, nameSerializerFactory, nameDeserializerFactory);
typeMapping.register(Name[].class, nameArrayTypeQname, nameArraySerializerFactory,
nameArrayDeserializerFactory);
typeMapping.register(Outer.Inner.class, innerTypeQname, innerSerializerFactory, innerDeserializerFa
typeMapping.register(IndexedNames.class, indexedPropertyBeanTypeQname,
indexedNamesSerializerFactory, indexedNamesDeserializerFactory);
Call call = newCall(service, port);
return call;

Serialization error in SAP Web Service.

Hi all,
I have exposed a custom RFC as a Web Service. This is a simple web service that returns Customer Data (from kna1) based on the Customer ID which we provide as input.
In the RFC, I have declared an internal table (G_RET) in the tables section of the RFC.
Now, while testing the web service, I can see a check box with NULL option beside the G_RET. If i check the NULL option for G_RET, I get an error.
XML Serialization Error. Array Property [Item] in class [none] must not have NULL elements. This is restricted by schema description.
This is a high priority task. Please reply to me with any solution that you may have.
Regards,
Preksha.

Your problem has nothing to do with SAP web service. When you expose a RFC function as a web service, you are defining a service contract using WSDL technologies and XML message format enforced by the schema definition associated with the data source.
When a system consume a web service it is upto that system to provide a client framework so that it can provide an implementation enforces by the WSDL contract. Contract terms in WSDL is only applicable to data types, message types, access style and ecoding.
It is upto the client framework to provide a mechanism to send and receive the data as per the contract.
In your case, you are using a Microsoft client, so MS implementation of web service technology play a big role here.
C# XML serialization class from the MS client program you are using to call the program, read the WSDL contract and try to understand the definition and terms and conditions of the messages, types, binding.
In your WSDL you may have constraints applied at each field level of the schemas associated with the input and output messages of the web service methods.
Unfortunatly the way C# XML serialization class understand the terms and condition is confusing and it create a rum time error.
Having said this all stories now let us get into practical way.
1. Test ur web service using a non MS client
2. Make sure it is working, this isolate your issues to the way client understanding the WSDL contracts.
3. Then work with some MS guys in your shop to address this issue.
From your post I hope you are a candidate having experience in working with SAP customization project. However when ever you deal with open technologies such as JAVA, Web Services, it is highly recomended to think outside the BUNN.
AS SAP move towards more open technologies such as JAVA, WSDL, SOAP, WS, XML, XSD it is very important to elaborate your knowledge beyond the scope of a customization project.
Thanks

Serialization error ArrayOfstring

I made a Web Service application with Java WSDP and have one function returning a String[].
I deployed my WS using deploytool and in the wsdl documenent I have:
<complexType name="ArrayOfstring">
<complexContent>
<restriction base="soap-enc:Array">
<attribute ref="soap-enc:arrayType" wsdl:arrayType="string[]" />
</restriction>
</complexContent>
</complexType>
I build a Dynamic proxy client calling my function by I have the following error when I run my client:
serialization error: no serializer is registered for (null, {http://wombat.com/xsd/MyWebService}ArrayOfstring
So, what should I do ?

http://forum.java.sun.com/thread.jsp?forum=331&thread=355816
Use the above post as an example.

No serializer found for class com.sun.xml.messaging.saaj.soap.ver1_1.Messag

Hi,
I am developing a soap web service using apache axis tool. I am using tomcat6 and jdk6. I need to return SOAPMessage as return object from remote interface methods. Now I have success fully deploy web service in tomcat. Also I have create client too, but when I am trying to call web service throw client then it show me a exception on client is
org.xml.sax.SAXParseException: Premature end of file.
and on server log, it show me this exception
java.io.IOException:
xisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.io.IOException: No serializer found for class com.sun.xml.messaging.saaj.soap.ver1_1.M
ssage1_1Impl in registry org.apache.axis.encoding.TypeMappingDelegate@98062f
faultActor:
faultNode:
faultDetail:
       {http://xml.apache.org/axis/}stackTrace:java.io.IOException: No serializer found for class com.su
.xml.messaging.saaj.soap.ver1_1.Message1_1Impl in registry org.apache.axis.encoding.TypeMappingDelegate@
8062f
       at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1507)
       at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
       at org.apache.axis.encoding.SerializationContext.outputMultiRefs(SerializationContext.java:1055)
       at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:145)
       at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
       at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
       at org.apache.axis.Message.writeTo(Message.java:539)
       at org.apache.axis.transport.http.AxisServlet.sendResponse(AxisServlet.java:902)
       at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:777)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
       at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:2
0)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:58
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
       at java.lang.Thread.run(Thread.java:619)
       {http://xml.apache.org/axis/}hostname:EMRG-409964-L19
ava.io.IOException: No serializer found for class com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl
n registry org.apache.axis.encoding.TypeMappingDelegate@98062f
       at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:317)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
       at org.apache.axis.Message.writeTo(Message.java:539)
       at org.apache.axis.transport.http.AxisServlet.sendResponse(AxisServlet.java:902)
       at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:777)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
       at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:2
0)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:58
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
       at java.lang.Thread.run(Thread.java:619)
aused by: java.io.IOException: No serializer found for class com.sun.xml.messaging.saaj.soap.ver1_1.Mess
ge1_1Impl in registry org.apache.axis.encoding.TypeMappingDelegate@98062f
       at org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1507)
       at org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
       at org.apache.axis.encoding.SerializationContext.outputMultiRefs(SerializationContext.java:1055)
       at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:145)
       at org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
       at org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
       ... 19 moreI have deploy new version of saa-impl.jar and saaj-api.jar too. And I also have deploy webservice-rt.jar too in server lib and application lib folder. but still this exception is there. I dont understand, how can I over come from this error. If some one have resolved this type of exception then please reply. Please reply me on [email protected]
--Thanks in Advance
Umashankar Adha
Sr. Soft. Eng.
United States

FYI, now I'm in work:
import javax.xml.namespace.*;
import javax.xml.rpc.*;
import javax.activation.*;
import javax.mail.*;
import com.sun.xml.messaging.saaj.*;
-classpath D:\jwsdp-1.3\jaxp\lib\endorsed\dom.jar;D:\jwsdp-1.3\jaxp\lib\endorsed\xercesImpl.jar;D:\jwsdp-1.3\saaj\lib\saaj-impl.jar;D:\jwsdp-1.3\saaj\lib\saaj-api.jar;D:\jwsdp-1.3\jwsdp-shared\lib\activation.jar;D:\jwsdp-1.3\jwsdp-shared\lib\mail.jar;D:\jwsdp-1.3\jaxrpc\lib\jaxrpc-api.jar;D:\jwsdp-1.3\jaxrpc\lib\jaxrpc-impl.jar;D:\jwsdp-1.3\jaxrpc\lib\jaxrpc-spi.jar;D:\jwsdp-1.3\jwsdp-shared\lib\jax-qname.jar
Those are what I had to use to get it working.
Chris

Serialization error for object (IDOC error 51)

hello,
Can Somebody help me with this??? this is what it gives me when the IDOC comes to the receiver instance (SAP R/3). The error code is 51.
Serialization error for object 01,S,12000677 . Expected counter 000001 < 000044 in IDoc
Message no. 5-300
Diagnosis
A serialization error has occurred for the HR object 01,S,12000677 that was received from the logical system E3B.
The expected serialization counter has the value 000001. However, the serialization counter in the IDoc has the value 000044 and is therefore too big. There are therefore older IDocs with this HR object with the serialization counter values in between. These IDocs have either not yet been posted, or have been posted incorrectly.
Procedure
Post all IDocs that have not yet been posted or that were posted incorrectly.
Thank you very much
PM

Hi David,
Please take a look at these threads..
Status code 51
IDOC Status 51
IDoc cannot be opened Error 51 (Inbound)
InfoPackage loading giving IDOC Error: Status 51
cheers,
Prashanth

Serialization error: no serializer is registered for class BasicDynaBean

Similar Messages

Maybe you are looking for