Serialization Error

When trying to export a Quictime movie to mpeg2 (using Quicktime 7 Pro) I get the following message;
Serialization Error
DVD Studio Pro must be serialized first in order to run Quicktime mpeg encoder.
I get the same error message when exporting from Final Cut Pro 5 and when using Compressor, it fails citing "Media server application unexpectedly quit".
I'm using the latest versions of DVDSP, Final Cut and Quicktime, can anyone help?

The old MPEG-2 encoder is superseded by Compressor 2. If you export from FCP using Compressor, does that work (using one of the DVD presets for MPEG-2)?
You should search for "serialization" in the DVDSP and QuickTime forums to see some of the many other discussions about this, including this one that talks about how to convince the old exporter to work:
http://discussions.apple.com/click.jspa?searchID=455964&messageID=1049698

Similar Messages

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

Serialization Error after adding a new field to BPM Process

Hi,
I have a BPM Process to which I added a new attribute userid and consuming the BPM process in a web dynpro application, I created a model using the BPM Process's Web Service but getting a serialization error that the model does not have a mandatory field with name [userid]. see below.
FYI.. I can trigger my BPM process through the Web Service in wsnavigator , the error I am getting is while executing the BPM Process from the custom webdynpro.
Any idea how to resolve the issue?
XML Serialization Error. GenericObject [
<modelObject class="com.sap.demo.wdpoc.wd.models.model.NewOperation"><attribute name="In" value="KK"/><attribute name="Name" value="133"/><attribute name="Age" value="dad"/><attribute name="Designation" value="12124"/><attribute name="Userid" value="null"/></modelObject>
] does not have a mandatory field with name [userid].
[EXCEPTION]
com.sap.engine.services.webservices.jaxrpc.exceptions.XmlMarshalException: XML Serialization Error. GenericObject [
<modelObject class="com.sap.demo.wdpoc.wd.models.model.NewOperation"><attribute name="In" value="KK"/><attribute name="Name" value="133"/><attribute name="Age" value="dad"/><attribute name="Designation" value="12124"/><attribute name="Userid" value="null"/></modelObject>
] does not have a mandatory field with name [userid].
at com.sap.engine.services.webservices.jaxrpc.encoding.SerializationUtil.serializeGenericFieldContent(SerializationUtil.java:1546)
at com.sap.engine.services.webservices.jaxrpc.encoding.SerializationUtil.serializeGenericFields(SerializationUtil.java:1431)
at com.sap.engine.services.webservices.jaxrpc.encoding.SerializationUtil.serializeGenericType(SerializationUtil.java:1383)
at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.serialize(GeneratedComplexType.java:168)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.serializeParameter(SOAPTransportBinding.java:1731)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.serializeRequest(SOAPTransportBinding.java:1683)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.writeSOAPRequestMessage(SOAPTransportBinding.java:254)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1272)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:952)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:907)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.tc.webdynpro.model.webservice.model.WSGenericModelClassExecutable.execute(WSGenericModelClassExecutable.java:73)
at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModelClassExecutable.execute(WSTypedModelClassExecutable.java:49)
at com.sap.demo.wdpoc.wd.comp.wdpoc.Wdpoc.execute(Wdpoc.java:257)

This question is not answered but I am marking it answered because I have to post more.
Sorry
-Ashwani

XML Serialization Error- While testing BAPI turned Web service

I have a requirement to create sales order in SAP R/3 from an e-commerce site. I went through many forums suggesting "exposing FMs into Web Service". I wrapped BAPI_SALESORDER_CREATEFROMDAT2 and BAPI_TRANSACTION_COMMIT into one FM and exposed as Web Service. I did a successful test-sequence.
When I tested the web service without giving values I got a response asking for "Sold-to Party or Ship-To Party". While testing the Web service with some values, I got the below error -
XML Serialization Error. Object content does not correspond to Schema restrictions of type [urn:sap-com:document:sap:rfc:functions][numeric4].
The e-commerce team tried to hit the Web service and got the below error-
IWAB0383E Error validating parameters
Note: Our servers does not have any ENHPacks. Only ECC 6.0.
Please suggest what might have gone wrong and how to resolve this.
Thanks!

Hi Gourav Khare,
I have created WSDL file through function module in SAP-ECC 5.0v.
I have followed below steps:
Crated FM (SE37)
Crated Web-service (SE37)
Generated WSDL file using (WSADMIN)
And consumed WSDF file in SOAP UI (SOAP UI 4.5.2 Trailer version)
Problem is: while consuming WSDL file in SOAP UI I getting ‘Serialisation failed’
For your reference I have furnished xml string below.
SOAP UI Input:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:sap-com:document:sap:rfc:functions">
<soapenv:Header/>
<soapenv:Body>
<urn:YSDF_INV_PRINT_FINAL_RFC_WS_N>

<PWR_INVOICE>
<INVOICE_SHIPPED_LINE>

<item>
<POSITION1></POSITION1>
<SALES_PART></SALES_PART>
                  <PART_DESC></PART_DESC>
<PRICE></PRICE>
<QUANTITY></QUANTITY>
<CUSTOMER_TAX_NO></CUSTOMER_TAX_NO>
<PROD_NONINVENTORY></PROD_NONINVENTORY>
<PROD_TAXABLE></PROD_TAXABLE>
<TAX_LEVEL></TAX_LEVEL>
</item>
</INVOICE_SHIPPED_LINE>
<INVOICE_NO></INVOICE_NO>
<ORDER_NO></ORDER_NO>
<DATE_PRINTED></DATE_PRINTED>
<DIV_CD></DIV_CD>
            <LAST_COST_INVOICE></LAST_COST_INVOICE>
<DELETE_ZERO_COST></DELETE_ZERO_COST>
<DELETE_NON_SHIPPED></DELETE_NON_SHIPPED>
<GLOBALREF></GLOBALREF>
<ORIGIN></ORIGIN>
<ORIGINID></ORIGINID>
</PWR_INVOICE>
</urn:YSDF_INV_PRINT_FINAL_RFC_WS_N>
</soapenv:Body>
</soapenv:Envelope>
SOAP UI Output:
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Body>
<soap-env:Fault>
<faultcode>soap-env:Client</faultcode>
<faultstring xml:lang="en">Serialisation failed</faultstring>
<detail>
<n0:SimpleTransformationFault xmlns:n0="http://www.sap.com/transformation-templates">
<MainName>/1BCDWB/WSS0130716111624448000</MainName>
<ProgName>/1BCDWB/WSS0130716111624448000</ProgName>
<Line>8</Line>
<Valid>X</Valid>
<ReferenceFault>
<DescriptionText>Error accessing the ref. node 'INVOICE_ID'</DescriptionText>
<RefName>INVOICE_ID</RefName>
</ReferenceFault>
<Caller>
                  <Class>CL_SRG_RFC_PROXY_CONTEXT</Class>
<Method>IF_SXML_PART~DECODE</Method>
<Positions>1</Positions>
</Caller>
</n0:SimpleTransformationFault>
</detail>
</soap-env:Fault>
</soap-env:Body>
</soap-env:Envelope>
And one more things are
I don't know the exact reason, but now the WSDL is working fine. No Idea, will it be consistent.
No changes in import and export parameters of RFC and no change in code, even if the logic is changed it should not affect the output on SOAP UI but in my case it does.
Wonder why all this happens, I cannot explain the exact reason technically because my RFC works fine every time, only issue is with SOAP UI.
From SAP point of view FM is working fine, and input parameter of FM is optional, validations are done by the programming logic and it will capture the message and its details with respect to input data.
I am not sure SOAP will work consistently and we are using ECC 5.0 most of the t-code not there like "SOAMANAGER" and all.
Kindly help me on this
Thanks & Regards,
   Akshath.L.T

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

HR Master data serialization error

Hi,
I activated serialization on sender and receiver system:
(Transaction SALE -> Modelling and Implementing Business Processes -> Configure Predefined ALE Business Processes -> Human Resource -> Master Data Distribution - > Serialize HR Master Data)
After processing, some iDocs have status 51 - Serialization error for object &. Expected counter 000001 < 000002 in IDoc.
I understand that when I get iDoc with too big serialization counter the iDoc should have status 66 (IDoc is waiting for preceding IDoc (Serialization)) and I should be able to reprocess the iDoc when I get iDocs with missing serialization counter. Am I right?
So why do they have status 51 and not 66?
Thanks for answer in advance.

there is some inconsistency in the receiver system.
for ex:
sender system Company code is different from the receiver system. etc...
Edited by: Ashok Kumar Reddy N on Feb 6, 2008 1:46 PM

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 in inbound idoc

Hi Friends
Am getting inbound idocs with this error : Serialization errror for object 01,S, 34343434,Expected counter 000001<
and error in details says,
The expected serialization counter has the value 000001. However, the serialization counter in the IDoc has the value 000002 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.
Intrested Part is   i put check ( Selected ) on as per client suggestion in ,
IMG -> Sap Netweaver -> Application server ->Idoc Interface / Application Link Enabling (ALE ) -> Modelling and imple Business process -> Configure Predefine ALE Business Process -> Human Resource -> Master data Distribution ->Serialize HR Master Data -> ( Serialize HR Master data in ALE inbound processing ) ...   settings and i was getting this error but when i take back this check ( unselect ) flag   idoc posted successfully    Now am confuse i shd keep this or not because am getting data from diff countries also.
what shd i do for this few expert said i need to do some thing for Serialization so automatically system shd take care for this,
Need your support on this .
Regards
Meeta

I have been working with IDocs in a serilization-active HR-ALE system and have learned a few things along the way ....
- Serialization must be active in both sending/originating and receiving/destination systems. (Turn on flag in customizing, as you have already done).
- Both systems maintain a registry of HR objects that includes in each record the object type, object id, and serial counter. The serial counter is increased by one in the sending system every time the object is sent via ALE and increased by one when the object is correctly processed in the receiving system. The serial counter is passed in the E1PLOGI record of each object in the IDoc.
- When a similar serialization error is received (where the counter received is lower than the expected counter), the error message gives a little more detail:   "Decide what to do based on your own particular situation. Responses could range from ignoring or editing the IDoc, to manually adjusting the serialization counter in the registry of the receiving system to the expected value."
Options are therefore:
- Edit IDoc - can use IDoc test tool (WE19) to create and edit a copy for processing.
- Use transaction RE_RHALE_HRMDRGIN to maintain the serial counters
- Use transaction RE_RHALE_RGIN2IDOC to adjust the serial counters for the offending IDoc
I strongly recommend, however, that you take some time to further understand the serialization process before updating the counters manually. If you've turned on, then off, then on the serialization flag(s) through customizing, you might consider initializing the serial counters in both sending and receiving systems and starting from scratch.

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 when using Jheadstart LOV's

I am using Jheadstart 11.1.1.4.26 and JDev 11.1.1.5
I have 2 applications, One of them uses JHeadstart LOV's and drop downs throught and has no errors. The other application gets a serialization error on the task flow at runtime if I use a JHeadstart LOV. If I use all ADF Model LOV's it is happy.
I have spent hours comparing the 2 applications looking for what is causing the serialization error on the one app but not the other. I was under the impression that upgrading to the latest jheadstart fixed this problem on the good app. Upgrading has not fixed the other one though.
Can anyone shed some light on this for me?
Thanks,
Jim
<SessionBasedScopeMap> <writeScopeMap> ADFc: Scope object serialization failed (object not serializable), scope='pageFlowScope[WEB-INF/adfc-config-CgRefCodesDescriptor2.xml#CgRefCodesDescriptor2TaskFlow]', objectKey='jhsLovPopup', objectType='oracle.jheadstart.controller.jsf.bean.UIComponentBinder'.
<SessionBasedScopeMap> <writeScopeMap>
java.io.NotSerializableException: oracle.jheadstart.controller.jsf.bean.UIComponentBinder
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at oracle.adfinternal.controller.util.Utils.verifySerializable(Utils.java:341)
     at oracle.adfinternal.controller.state.SessionBasedScopeMap.writeScopeMap(SessionBasedScopeMap.java:122)
     at oracle.adfinternal.controller.state.PageFlowScope.writeObject(PageFlowScope.java:156)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at java.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1247)
     at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at java.util.Hashtable.writeObject(Hashtable.java:824)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at weblogic.servlet.internal.session.SessionData.writeExternal(SessionData.java:1095)
     at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1429)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1398)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at weblogic.servlet.internal.session.FileSessionContext.sync(FileSessionContext.java:407)
     at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2860)
     at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2835)
     at weblogic.servlet.internal.ServletResponseImpl$1.run(ServletResponseImpl.java:1485)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1479)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1462)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
<SessionBasedScopeMap> <writeScopeMap> ADFc: Scope object serialization failed (object not serializable), scope='pageFlowScope[WEB-INF/adfc-config-CgRefCodesDescriptor2.xml#CgRefCodesDescriptor2TaskFlow]', objectKey='jhsLovPopup', objectType='oracle.jheadstart.controller.jsf.bean.UIComponentBinder'.
<SessionBasedScopeMap> <writeScopeMap>
java.io.NotSerializableException: oracle.jheadstart.controller.jsf.bean.UIComponentBinder
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at oracle.adfinternal.controller.util.Utils.verifySerializable(Utils.java:341)
     at oracle.adfinternal.controller.state.SessionBasedScopeMap.writeScopeMap(SessionBasedScopeMap.java:122)
     at oracle.adfinternal.controller.state.PageFlowScope.writeObject(PageFlowScope.java:156)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at java.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1247)
     at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at java.util.Hashtable.writeObject(Hashtable.java:824)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1469)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at weblogic.servlet.internal.session.SessionData.writeExternal(SessionData.java:1095)
     at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1429)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1398)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330)
     at weblogic.servlet.internal.session.FileSessionContext.sync(FileSessionContext.java:407)
     at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2860)
     at weblogic.servlet.internal.ServletRequestImpl$SessionHelper.syncSession(ServletRequestImpl.java:2835)
     at weblogic.servlet.internal.ServletResponseImpl$1.run(ServletResponseImpl.java:1485)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1479)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1462)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

Thanks Stephen, You jarred my memory. It was the weblogic.xml settings. In the application without the serialization error I had commented out some persistence settings. When I did the same with the problem application the serialization error went away.
<?xml version = '1.0' encoding = 'UTF-8'?>
<weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd" xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">


</weblogic-web-app>

Service error - ECC_EMPTIMSHEETCHGRC - XML Serialization Error

I am not able to execute the service - EmployeeTimeSheetChangeRequestConfirmation_In (http://<host:port>/sap/bc/srt/xip/sap/ECC_EMPTIMSHEETCHGRC?sap-client=<number>&wsdl=1.1&mode=sap_wsdl) in the discovery system.
I am getting the following error - XML Serialization Error. Object content does not correspond to Schema restrictions of type [http://sap.com/xi/EA-HR/SE/Global][/wsdl:definitions/wsdl:types/xsd:schema[2]/xsd:complexType[48]/xsd:simpleContent/xsd:extension/xsd:attribute[2]/xsd:simpleType].
Procedure followed :
WSADMIN -> execute the service.
Pass the following values to create a new record for a employee.
Action code (02),
Work Agreement ID,
External ID,
item-> Category code,
Price -> Amount,
price -> base Quantinty
Full Working day indicator,
Employee time validity,
Quantity,
Amount,
Employee Time ID,
Employee Time item ID,
Sending Cost Center,
Activity Type,
Receiving cost center,
Receiver WBS element,
Weekday indicator.
Start date and end date
Please specify, why I am not able to execute the same.
I have already gone through the ES Workplace -> service details.
Kindly help.
- anto

This was resolved through a ticket. Error caused due to incompatible values or not skipping the relevant nodes. (Error raised due to poor documentation. The mandatory values specified were not required. on not passing the said mandatory values, the service works fine ).

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 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

Connection to Failed Service or Not Serializable Errors

Hi. I'm getting connection to failed service errors or not serializable errors when I run a production sized load for my project. I'm trying to generate 100,000 PDFs one at a time on each thread against the Output web service. I'm running custom code that makes the Output web service call on individual thread. I run up to 40 threads against my vertical cluster and occasionally I see a not serializable error or connection to failed service on my code. Any ideas on what could be the cause of the errors? Thank you for any insight you can provide.
I'm running a WebLogic vertical cluster on one box. 1 admin server of WebLogic 9.2 MP3 with 10 managed WebLogic servers on the same physical box in a cluster. I have enough RAM to support all these JVMs and the GDS is on the local drive on the box.
Environment details:
Software: Windows 2003 R2 SP2 (32-bit), WebLogic 9.2 MP3, Adobe LC 8.2.1 SP3 + QF 3.19, Oracle 10.2.0.4, BEA Jrockit 1.5.0_12 (32-bit)
Hardware: 2 CPU 2.8GHz * 4 cores * Hyper-Threading = makes it look like 16 CPUs in Task Manager, Performance tab, 16 GB RAM, 50+ GB HD space free
Error Message:
+ com.adobe.idp.dsc.DSCNotSerializableException: Not Serializable
IVS Error Message that happens randomly when the errors are occurring. I can resubmit the same IVS test where this error shows up on the managed WL instance and it :
java.lang.IllegalStateException: Connection to failed service. in com.adobe.livecycle.formsservice.exception.RenderFormException, cause: java.lang.IllegalStateException: Connection to failed service. in com.adobe.livecycle.formsservice.exception.FormServerException
Exception in Output Service
Stack Trace
at com.adobe.formServer.FormServer.renderForm(FormServer.java:210)
at com.adobe.formServer.FormServer.renderForm(FormServer.java:257)
at com.adobe.formServer.docservice.FormsDocService.renderForm(FormsDocService.java:483)
at com.adobe.printSubmitter.util.FormSubmitter.submit(FormSubmitter.java:157)
at com.adobe.printSubmitter.util.FormSubmitter.submit(FormSubmitter.java:94)
at com.adobe.printSubmitter.util.Splitter.endElementNoBatch(Splitter.java:175)
at com.adobe.printSubmitter.util.Splitter.endElement(Splitter.java:155)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch( Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:176)
at com.adobe.printSubmitter.PrintServer.execute(PrintServer.java:519)
at com.adobe.printSubmitter.PrintServer.submit(PrintServer.java:223)
at com.adobe.printSubmitter.service.OutputServiceImpl.generateOutputInTxn(OutputServiceImpl. java:247)
at com.adobe.printSubmitter.service.OutputServiceImpl.generatePDFOutputInTxn(OutputServiceIm pl.java:347)
at com.adobe.printSubmitter.service.OutputServiceImpl.access$100(OutputServiceImpl.java:79)
at com.adobe.printSubmitter.service.OutputServiceImpl$2.doInTransaction(OutputServiceImpl.ja va:313)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doRequiresNew (EjbTransactionBMTAdapterBean.java:218)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapter_jmbvky_ELOImpl.do RequiresNew(EjbTransactionBMTAdapter_jmbvky_ELOImpl.java:63)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:133)
at com.adobe.idp.dsc.transaction.impl.DefaultTransactionTemplate.execute(DefaultTransactionT emplate.java:79)
at com.adobe.printSubmitter.service.OutputServiceImpl.invokeGeneratePDFOutputWithSMT(OutputS erviceImpl.java:308)
at com.adobe.printSubmitter.service.OutputServiceImpl.generatePDFOutput(OutputServiceImpl.ja va:289)

Hi. I'm getting connection to failed service errors or not serializable errors when I run a production sized load for my project. I'm trying to generate 100,000 PDFs one at a time on each thread against the Output web service. I'm running custom code that makes the Output web service call on individual thread. I run up to 40 threads against my vertical cluster and occasionally I see a not serializable error or connection to failed service on my code. Any ideas on what could be the cause of the errors? Thank you for any insight you can provide.
I'm running a WebLogic vertical cluster on one box. 1 admin server of WebLogic 9.2 MP3 with 10 managed WebLogic servers on the same physical box in a cluster. I have enough RAM to support all these JVMs and the GDS is on the local drive on the box.
Environment details:
Software: Windows 2003 R2 SP2 (32-bit), WebLogic 9.2 MP3, Adobe LC 8.2.1 SP3 + QF 3.19, Oracle 10.2.0.4, BEA Jrockit 1.5.0_12 (32-bit)
Hardware: 2 CPU 2.8GHz * 4 cores * Hyper-Threading = makes it look like 16 CPUs in Task Manager, Performance tab, 16 GB RAM, 50+ GB HD space free
Error Message:
+ com.adobe.idp.dsc.DSCNotSerializableException: Not Serializable
IVS Error Message that happens randomly when the errors are occurring. I can resubmit the same IVS test where this error shows up on the managed WL instance and it :
java.lang.IllegalStateException: Connection to failed service. in com.adobe.livecycle.formsservice.exception.RenderFormException, cause: java.lang.IllegalStateException: Connection to failed service. in com.adobe.livecycle.formsservice.exception.FormServerException
Exception in Output Service
Stack Trace
at com.adobe.formServer.FormServer.renderForm(FormServer.java:210)
at com.adobe.formServer.FormServer.renderForm(FormServer.java:257)
at com.adobe.formServer.docservice.FormsDocService.renderForm(FormsDocService.java:483)
at com.adobe.printSubmitter.util.FormSubmitter.submit(FormSubmitter.java:157)
at com.adobe.printSubmitter.util.FormSubmitter.submit(FormSubmitter.java:94)
at com.adobe.printSubmitter.util.Splitter.endElementNoBatch(Splitter.java:175)
at com.adobe.printSubmitter.util.Splitter.endElement(Splitter.java:155)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch( Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:176)
at com.adobe.printSubmitter.PrintServer.execute(PrintServer.java:519)
at com.adobe.printSubmitter.PrintServer.submit(PrintServer.java:223)
at com.adobe.printSubmitter.service.OutputServiceImpl.generateOutputInTxn(OutputServiceImpl. java:247)
at com.adobe.printSubmitter.service.OutputServiceImpl.generatePDFOutputInTxn(OutputServiceIm pl.java:347)
at com.adobe.printSubmitter.service.OutputServiceImpl.access$100(OutputServiceImpl.java:79)
at com.adobe.printSubmitter.service.OutputServiceImpl$2.doInTransaction(OutputServiceImpl.ja va:313)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterBean.doRequiresNew (EjbTransactionBMTAdapterBean.java:218)
at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapter_jmbvky_ELOImpl.do RequiresNew(EjbTransactionBMTAdapter_jmbvky_ELOImpl.java:63)
at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:133)
at com.adobe.idp.dsc.transaction.impl.DefaultTransactionTemplate.execute(DefaultTransactionT emplate.java:79)
at com.adobe.printSubmitter.service.OutputServiceImpl.invokeGeneratePDFOutputWithSMT(OutputS erviceImpl.java:308)
at com.adobe.printSubmitter.service.OutputServiceImpl.generatePDFOutput(OutputServiceImpl.ja va:289)

Serialization Error

Similar Messages

Maybe you are looking for