Catching AMF serialization errors RO- AS?

Trying to get notifications when there are mismatches between Java RemoteObject and ActionScript DTOs.
Is it possible to somehow log/catch missing/extra properties when getting a remote object from the server (RO->AS)?
It works the other way around AS->RO.
LCDS enables server-side logging when getting unexpected properties (flag log-property-errors in channel's serialization).
From what I can google that's impossible unless creating a custom serializer, which is impractical.
Thanks.

Hi,
When the send fails, please try putting a break point and see
if the FaultEvent object has any other information on why this is
failing. Check the faultDetail, faultString and the rootCause
properties in the FaultEvent. You can also see URL of the channel,
see if the URL is proper.
You said when the browser is refreshed the problem is not
there anymore, is it because of swf file being cached?
Hope this helps.

Similar Messages

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

How to catch SAP application errors in BPM.

Hi,
I have a IDOC to Soap Sync Scenario where I send the message to a Webservice. I have used a BPM since we need to catch the resposne of this message and map it to a RFC. For ex if I get a success resposne I need to map success if not than I need to catch the error and map it to the RFC. Now here in some cases like if the target system (webservice) is down than XI raises a sap application error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Connection refused (errno:239)</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Normally XI stops the process in these cases and does not proceed to the next step but I need to catch this message and map the content in the AdditionalText to the target RFC. Can anyone let me know how to catch this SAP Application Error in BPM and map it to the RFC.
Thanks,
Bhargav

Hi Gaurav,
As I have mentioned I need to catch the application error in the BPM. If you see the discussion that is mentioned after the blog you have mentioned it is stated that the fault messages or the application error cannot be caught in BPM.
In the blog that you stated we can catch the fault message and map it to a message structure but only to that extent after that it would stop the BPM process at that step but would not proceed further as shown in the screenshot given in the blog it would fail as "application error restart not possible".
I need to proceed further and capture this error to an RFC Structure and call a proxy.
Here after the error it does not proceed to the next step.
Thanks,
Bhargav

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

How to catch CONVT_NO_NUMBER runtime error in ABAP Proxy

Hi all,
In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump and then stuck the whole queue. I noticed that this error cannot be caught by CX_ROOT exception class. So, how can I catch this runtime error and avoid the dump of our program?
Thanks,
YiNing

Hi,
While Executing the proxy,first give \h TC and then execute the proxy then it will automatically got to debugging mode.
I think ur data is worng,if it is wrong then only u will get this type of errors.
Regards,
Phani

Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Hi all,
       In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump. I noticed that this error cannot be caught by CX_ROOT exception class.
       Some told me I can use the CATCH SYSTEM-EXCEPTIONS sentence to catch this runtime error, but it is a old-way syntax and cannot be used with the "try" and "catch".
       So, how can I catch this runtime error and avoid the dump of our program?
Thanks,
YiNing

Hi,
You are not checking for conversion.
You are checking ofr logical expression.
Try below code, it works
DATA error_ref TYPE REF TO cx_sy_conversion_no_number.
DATA err_text TYPE string.
DATA a TYPE i.
TRY.
    MOVE 'A' TO a.
CATCH cx_sy_conversion_no_number INTO error_ref.
    err_text = error_ref->get_text( ).
    WRITE err_text.
ENDTRY.
Regards,
Atish

[svn:bz-trunk] 22429: Adding the default fallback of serializer and deserializer classes to amf deserializer and amf serializer

Revision: 22429
Revision: 22429
Author:   [email protected]
Date:     2011-09-07 08:04:46 -0700 (Wed, 07 Sep 2011)
Log Message:
Adding the default fallback of serializer and deserializer classes to amf deserializer and amf serializer
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/SerializationContext.java

How to user Error Trigger for mapping - trying to catch row-based errors

Hello everyone,
Has anyone managed to use the error trigger for a mapping?
I created a row based map with the right parameters (i set the error trigger procedure which I already created in the database).
For this map after run i have 5 warnings which appear in the interface but the error trigger procedure is not executed.
I set the max errors to 3 so after run the map should end with errors instead of warnings.
Still not executing the error trigger procedure.
What am i doing wrong?
Please help as i really need a way to "catch" row based errors - having multiple target tables sucks.
Thank you,
Irina
Edited by: Irina on Jul 30, 2009 1:32 PM
Edited by: Irina on Jul 30, 2009 3:38 PM

It seems nobody knows what I'm talking about - no documentation on it either ... not even in the user guide ... not even on google ... well, just saying what it is doesn't count :D

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

Catching a runtime error

Hi,
A runtime error for overflow (type p) occurs with the following details:
Runtime Errors         COMPUTE_BCD_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
Date and Time          06/12/2007 11:33:13
Instead of displaying the dump screen, i'd like to catch the runtime error and display a message instead. The following is the code that causes the error (onhand is too large):
      REQRMENT = FORECAST - ONHAND - OPENQTY.
Please help,
Points will be rewarded and all help will be greatly appreciated.
Thanks,
John

According to help, these are the catchable exceptions for a form call:
Catchable Exceptions
CX_SY_PROGRAM_NOT_FOUND
Cause: The specified program was not found.
Runtime Error: LOAD_PROGRAM_NOT_FOUND
Cause: The specified program cannot exist because the program name is longer than 40 characters.
Runtime Error: PERFORM_PROGRAM_NAME_TOO_LONG
CX_SY_DYN_CALL_ILLEGAL_FORM
Cause: The specified subroutine was not found.
Runtime Error: PERFORM_NOT_FOUND
Cause: The specified index was too small.
Runtime Error: PERFORM_INDEX_0
Cause: The specified index was negative.
Runtime Error: PERFORM_INDEX_NEGATIVE
Cause: The specified index was too large.
Runtime Error: PERFORM_INDEX_TOO_LARGE
CX_SY_DYN_CALL_PARAM_MISSING
Cause: The called FORM expects more parameters than were specified.
Runtime Error: PERFORM_PARAMETER_MISSING
CX_SY_DYN_CALL_PARAM_NOT_FOUND
Cause: More parameters were specified than expected by FORM.
Runtime Error: PERFORM_TOO_MANY_PARAMETERS
CX_SY_DYN_CALL_ILLEGAL_TYPE
Cause: In the parameter transfer using the addition STRUCTURE, the addressing offsets/> do not match in the current and target structures.
Runtime Error: PERFORM_BASE_WRONG_ALIGNMENT
Cause: The deep components contained in the current and target structures cannot be passed to each other. This error can only occur in parameter transfer using STRUCTURE.
Runtime Error: PERFORM_CAST_DEEP_MISMATCH
Cause: During the transfer of a generically defined type to the form, a type conflict occurred.
Runtime Error: PERFORM_CONFLICT_GENERIC_TYPE
Cause: The table type of the current parameter does not match the table type of the parameter defined in the form.
Runtime Error: PERFORM_CONFLICT_TAB_TYPE
Cause: The type of current parameter does not match the type of parameter defined in the form.
Runtime Error: PERFORM_CONFLICT_TYPE
Cause: The current parameter occupies less storage space than the target parameter defined in the form. This error occurs only with parameter specification using STRUCTURE.
Runtime Error: PERFORM_PARAMETER_TOO_SHORT
Cause: During parameter transfer with the addition STRUCTURE, the fragment views of the current and target parameters do not match. This error only occurs in Unicode programs in
Runtime Error: PERFORM_CONFLICT_UC_STRUCT
Cause:When the form is called, an internal table is expected as current parameter.
Runtime Error: PERFORM_TABLE_REQUIRED
Cause: A hash table was passed to a parameter defined using TABLES.
Runtime Error: PERFORM_STD_TAB_REQUIRED

Catching AMF serialization errors RO- AS?

Similar Messages

Maybe you are looking for