HL7 message body serialization error

does anyone know what this error implies?
Error happened in body during serialization
Error # 1
Alternate Error Number: 301
Alternate Error Description: Invalid tag Id found 'ZPD'
Alternate Encoding System: HL7-BTA

Hi,
According to the error, maybe that you are using multi-part message with Zsegments. If we use an undeclared Z segment, which the integration engine will not process according to the message schema. For more information about this type
of Z segment, see
Handling Undeclared Z Segments.
Hope it can help you.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place. <br/> Click <a
href="http://support.microsoft.com/common/survey.aspx?showpage=1&scid=sw%3Ben%3B3559&theme=tech"> HERE</a> to participate the survey.

Similar Messages

Accessing the original message body in Error handler

Hello everybody,
The loanGatewy3 proxy service in the OSB tutorial uses a stage in the request pipeline for validation. If a validation error occurs the error handler reports the original body message using a reporting action.
Now if an error happens inside the Routing node; and if an error handler is defined to report the original message ($body), the reporting action will report the error message not the original message. It seems that the $body variable contains the erroneous response instead of the original message. So is there a way to access the original request $body inside a node error handler?
Best regards,
Tarek

you can always put the original message into a dummy variable $origMessage, then in the event of an error report on $origMessage not $body
cheers
James

Q10 Pin message body download error

I have updated the software to the latest version. Removed the battery and added back again. Still no success. In my role I receive and send pin messages. I do receive pin messages which are email forwarded as pin message. Urgently need help.

Hello yoghini,
Welcome to the forums.
Was this functionally working before you did the update? What is the exact error you are getting when you try to view these PIN messages?
-SR
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

Download error, message body could not be downloaded

Someone please help me with this. I've had the Q10 since it came out and ever since I've had it there are emails that will just not open. These emails are simple text emails. I thought this was normal and didn't think anything of it until I spoke to a coworker who also has a Q10 and he is not having the same issue. So I searched high and low to try and find a solution and nothing.
To be clear this only happens to a few emails.
I tried pulling the battery.
I tried software updates. I am running BB 10 OS Software Release 10.1.0.238. Nothing better then this available.
I tried deleting anything older emails since I did see somewhere in my search for an answer that there maybe an old email with odd characters causing the issue.
Still nothing.
When I open the email I get the header info i.e.. Who it was sent to, from and subject. I get the flower with the word image001.jpg and the size of the file (again this is a txt file no images). And in the middle of the screen I get the circle going around for about a minute as if it's loading and then the error pops up;
Download Error
Message body could not be downloaded
Cancel OK
hitting Cancel or OK just brings me back to my list of emails
Any suggestions of fixes would be appreciated.

i have the same " download error " but with BBM invites

Getting error while mapping HL7 message to Backend message

Hi all,
can anybody help me in this regard,
i am doing mapping between HL7 message fields and backend fields and here HL7 message is target message and i am getting error when i tested my mapping.
error is: " min != max "
why this error is comming?
i mapped all mandatory(which are shown in red color) target fields to empty constant. but still on of the field is in red. is that the reason for this error or something else? if yes then why that field is still in red even after mapping to empty constant?
Thanks and Regards,
Ujwalkumar

hi
check for the following:
1.check for the occurence of the segments
2.map the parents with empty constants or with resp soruce segmetns
3. donot map empty constants to mandatory field in a segments

CFPOP error -- java string in message body

I'm using CFPOP to do a very typical pop mail check and then
I throw the message parts into a few fields in a database: subject,
body, and also textbody and htmlbody if the message comes through
as multi-part. I got a very weird row in the database this morning.
Subject looks good, but the body of the message is:
"javax.mail.internet.MimeMultipart@12496a" and the textbody and
htmlbody fields are blank. I also pull down attachments into a
folder and there were no attachments for this message. Any ideas
what this means and what might have happened to the message body?
Thanks in advance. -Rachel

Getting
javax.mail.internet.MimeMultipart@12496a is indeed odd. It
looks like the memory address of a
MimeMultipart
object.
Such an object may embody plain text body, HMTL body and
attachments, each separated from the others by a so-called
boundary. Perhaps the message did not have clear boundaries between
the parts. Or it might have contained a part having a MIME type
that Coldfusion does not recognize.

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

Problems with B2B Editor validating HL7 Messages

Hi all,
I am having some problems related to B2B Document Editor and HL7 messages.
When we ran the Analyzer with the following document:
MSH|^~\&|ALERT|CHVNG|CPCHS|CHVNG|20070409145826+0000||OMG^O19^OMG_O19|1|P|2.4|
PID|||303030^^^SONHO^NS||Patient^Alert||19840412000000+0000|M|||ESTRADA DA BARROCA, LOTE C O, FRT^^ENTRONCAMENTO^^2430|||||||^^^CHVNG|
PV1||URG|1^33^^1||||||||||||||||27041729^^^CHVNG||||||||||||||||||||||||||||||||V|
ORC|NW|100^ALERT|||||||20070409145813+0000|||123^Teste^M\XE9\dico^^^^^^^^^^ON|||||2000^RADIO TEXT^CHVNG|
OBR||100^ALERT||M11020^Abd\XF3\men Simples Em P\XE9\^RADIO||||||||||||123^Teste^M\XE9\dico^^^^^^^^^^ON|
NTE|||dor abdominal|
we received the following message:
"The data starting at position 510 is not a valid EDI interchange. The remainder of the data file was ignored. "
It identifies the header (MSH Segment) well, but it can not identify the message body.
It is very strange, because we've selected HL7 as the message format on the previous step but aparently this message is a EDI format message. This message occurs on any file we have or with any HL7 message found on the internet (http://www.dt7.com/cdc/sampmsgs.html)
We can open the document with the Data Editor, but if we change any value and save it, it is impossible to open the message with the Analyzer:
"The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect."
We are running the B2B Document Editor version 6.0.0.1471 with the 6.0.4.84 version of HL7 Database version.
Can you give us any advice ?
Cheers,
Rodrigo Nascimento

Hello,
As per Jeff's post even we have observed OD OA at the end of the line. Please use a hex editor or B2B document editor to correct the same. We have done the above steps and are not getting the mentioned errors. HTH.
Please let us know.
Rgds,Ramesh

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: no serializer is registered for class BasicDynaBean

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

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

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

XML Message Body Selector in Automation

Hi,
I'm having some trouble implementing a XML Message Body Selector in an automated task. I'm running OSM 7.2.0.7 in a Unix environment and using Design Studio 7.2.1.
I'm sendind in my request to an external system a request tthe following string: OSM-TaskName-%{CARTRIDGE_VERSION}
<Request>
    <Header>
        <dueDate>20131128</dueDate>
        <application>OSM-MSS_Lookup-1.0.0.0.5</application>
    </Header>
</Request>
The response of MSS is:
<Response>
    <Header>
        <dueDate>20131128</dueDate>
        <application>OSM-MSS_Lookup-1.0.0.0.5</application>
    </Header>
In the selector I've tried different XPath expressions:
Select:
/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']/text()
*[local-name() ='Responset']/*[local-name()='Header']/*[local-name()='application']/text()
//*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']/text()
/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']
*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']
//*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']
/Response/Header/application
/Response/Header/application/text()
Compare: OSM-MSS_Lookup-%{CARTRIDGE_VERSION}
I keep getting the following error in the log file for the differente selectors:
####<Nov 28, 2013 10:34:31 AM CST> <Info> <oms> <hostname> <SOM_ManagedServer_1> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'
> <sceadmin> <BEA1-49AB960B7AE5258D5CC8> <0710a255d6bbb54d:-1d6ed94c:142960580fb:-8000-0000000000026363> <1385656471431> <BEA-000000> <api.e:
        namespace/version: SOM_Cartridge/1.0.0.0.5
        automator type: taskAutomator
        plugin JNDI name: MSS_Lookup.automatedtask.somprovisioning.MSS_LookupReceiverBean
        plugin class name: oracle.communications.ordermanagement.automation.plugin.XQueryReceiver
        run plugin as: oms-automation   receiver:
                type: external
                JMS source: sky/MSS/Product/WebServiceResponseQueue
                message [property|body] selector: JMS_BEA_SELECT('xpath', '/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']')='OSM-MSS_Lookup-1.0.0.0.5'
####<Nov 28, 2013 10:34:31 AM CST> <Warning> <EJB> <hostname> <SOM_ManagedServer_1> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <oms-automation> <> <0710a255d6bbb54d:-1d6ed94c:142960580fb:-8000-000000000002650a> <1385656471454> <BEA-010061> <The Message-Driven EJB: MSS_Lookup.automatedtask.somprovisioning.MSS_LookupReceiverBeanMDB is unable to connect to the JMS destination: sky/MSS/Product/WebServiceResponseQueue. The Error was:
javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "JMS_BEA_SELECT('xpath', '/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']')='OSM-MSS_Lookup-1.0.0.0.5'"
Nested exception: javax.jms.InvalidSelectorException: weblogic.messaging.kernel.InvalidExpressionException: Expression : "JMS_BEA_SELECT('xpath', '/*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']')='OSM-MSS_Lookup-1.0.0.0.5'"
I would appreciate any help or ideas.
Cheers

Hi,
Could you confirm on below:
1 ) Are you using multiple automation plug-in external event receivers in the same automation task ?
2 ) And are you having the default Correlation Message property set to 'JSMCorrelationID' in external event receiver?
If your answer for the first question is No, they i would suggest to use Correlation XML Body as
*[local-name() ='Response']/*[local-name()='Header']/*[local-name()='application']
The value of the field(application) in request must match the value of the field in response, in your case it is matching. And you will be reading this correlation id in response processing xquery.
Regards
Srinivas

Orchestration exception:Exception occurred when persisting state to the database because of special character ' ' in HL7 message.

In some scenarios HL7 message is coming with special character ‘’ and HL7 dis-assembler escaping this character with “”. But while sending out (pass thru pipeline but orchestration trying to persist here at last sendshape.) from orchestration
this message failing with the error “Exception occurred when persisting state to the database.”
As per the analysis , Orchestration is unable to convert to xml document from a
XLANGMessage because of this special character. We have tried to call custom .net class with following code and its failing here as well (I think orchestration also trying to do same way and failing with the message and failing with same error.).
public void ProcessRequest(XLANGMessage reqMessage)
XmlDocument xmlDocument = (XmlDocument)reqMessage[0].RetrieveAs(typeof(XmlDocument)); It is failing here with the error
“ ', hexadecimal value 0x10, is an invalid character. Line 1, position 1865. “
Note : Please find the special character in the attachment circled in red color.

Hi ,
Please find the xml and the screenshot.
<OBX_ObservationResult>
<OBX_1_SetIdObx>3</OBX_1_SetIdObx>
<OBX_2_ValueType>TX</OBX_2_ValueType>
<OBX_3_ObservationIdentifier>
<CE_0_Identifier>P.112</CE_0_Identifier>
<CE_1_Text>Where pt. will be transported to \T\ where famly can wait:</CE_1_Text>
</OBX_3_ObservationIdentifier>
<OBX_4_ObservationSubId />
<OBX_5_ObservationValue>Y</OBX_5_ObservationValue>
<OBX_6_Units>
<CE_0_Identifier />
</OBX_6_Units>
<OBX_7_ReferencesRange />
<OBX_8_AbnormalFlags />
<OBX_9_Probability />
<OBX_10_NatureOfAbnormalTest />
<OBX_11_ObservationResultStatus>N</OBX_11_ObservationResultStatus>
</OBX_ObservationResult>

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

HL7 message body serialization error

Similar Messages

Maybe you are looking for