Title: Bean serialization problem

You need to specify the Serializer in the deploy.wsdd file.  I have found that when no Serializer is specified, Axis will generate this error.  See the UserGuide on how to setup simple serializers for classes that follow the Bean pattern.  If these simple Serializers do not work, then you will have to build a custom Serializer.  NOTE: you need to specify a Serializer for all complex types including any java native array types.

 

Jim Stickley

Birch Telecom

(816) 300-6743

[EMAIL PROTECTED]

 

-----Original Message-----
From: Christian Schmitz [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 12, 2002 11:12 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Bean serialization problem

 

Hi,

could be that I had the same problem. Look at the namespace entries you set in your deployment mapping and in your client mapping.

Regards

Christian


[Christian Schmitz] 

 -----Original Message-----
From: Michael Roytman [mailto:[EMAIL PROTECTED]]
Sent: Freitag, 12. Juli 2002 17:54
To: [EMAIL PROTECTED]
Subject: Bean serialization problem

Hello,

I have been playing with Axis beta2 (with Tomcat 4.0.4) for a couple of days.
I have deployed a simple webservice as jws file that returns my PayResponse bean.
I am having problems with bean serialization when calling a method, here is the trace from tcpmon:

<html><head><title>Apache Tomcat/4.0.4 - Error report</title><STYLE><!--H1{font-family : sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;} BODY{font-family : sans-serif,Arial,Tahoma;color : black;background-color : white;} B{color : white;background-color : #0086b2;} HR{color : #0086b2;} --></STYLE> </head><body><h1>Apache Tomcat/4.0.4 - HTTP Status 500 - Internal Server Error</h1><HR size="1" noshade><p><b>type</b> Exception report</p><p><b>message</b> <u>Internal Server Error</u></p><p><b>description</b> <u>The server encountered an internal error (Internal Server Error) that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>java.io.IOException: No serializer found for class com.uls.cto.cardsafe.PayResponse in registry org.apache.axis.encoding.TypeMappingImpl@bc5596

Generated WSDL looks fine, PayResponse bean is a complex type:

- <complexType name="PayResponse">
- <sequence>
<element name="returnCode" type="xsd:int" />
<element name="errorMessage" nillable="true" type="xsd:string" />
<element name="txRefNumber" nillable="true" type="xsd:string" />
</sequence>
</complexType>

I've looked through mailing list archives but still can't get it to work.
Any help is greatly appreciated.
Thanks,

-----
Michael Roytman, Senior Software Engineer   
UAL Loyalty Services           
1375 E. Woodfield Rd, #300      Phone   847-969-8150 x 4515 
Schaumburg, IL 60173    Fax     847-969-8164

Reply via email to