RE: Deserializer help needed

[Daniel Smeltzer]

Title: Message

Thanks a ton!  You have saved me a great amount of time.  Thanks again!

 

Daniel

-----Original Message-----
From: Gurkan, Ozzie (MAN-Corporate) [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 11, 2003 12:49 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Deserializer help needed

Here are the two attached files for helping with serialization and de-serialization of Castor EnumType classes. You will need to add the following to your wsdd file:

 

 

<typeMapping deserializer="org.apache.axis.encoding.ser.castor.CastorEnumTypeDeserializerFactory" qname="ns19:myEnum" serializer="org.apache.axis.encoding.ser.castor.CastorEnumTypeSerializerFactory" type="java:com.company.MyEnumType" xmlns:ns19=http://mycompany.com//>

 

Notice the reflection takes place on the serializer to pull out the string (call "toString" method) and likewise on the deserializer to create the object (call static "valueOf" method). The deserializer also produces the schema entry needed for the WSDL generation.

 

Enjoy!

 

Ozzie Gurkan

Manheim

 

-----Original Message-----
From: Daniel Smeltzer [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 11, 2003 1:42 PM
To: [EMAIL PROTECTED]
Subject: RE: Deserializer help needed

That would be greatly helpful!  Thanks!

-----Original Message-----
From: Gurkan, Ozzie (MAN-Corporate) [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 11, 2003 12:39 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Deserializer help needed

I have tackled this problem with Castor EnumType classes. If you like, I can attach the source code and you can duplicate it. It also automatically generates the schema needed for WSDL generation.

-----Original Message-----
From: Daniel Smeltzer [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 11, 2003 1:37 PM
To: [EMAIL PROTECTED]
Subject: Deserializer help needed

I need help finding information about writing a custom deserializer.  I have a class I want to pass through Axis that acts as a type-safe enumeration.  It has no public constructor.  The class can return an instance that is matched against certain data, but no new instances are ever created (they are all created in a static initializer).

This being the case, the bean deserializer is of no use.  I'm having difficulty finding information about the deserialization process.  Aside from the source code, are there any good references to Axis deserializers?  Anybody else tackle a similar problem?

Thanks for all help.

Daniel

 

Statement of Confidentiality

This e-mail message, and any attachments, is confidential and is intended solely for the addressees named above.  If you are not a named recipient, an individual specifically authorized to receive this communication, or if this message has been addressed to you in error, do not read, disclose, reproduce,  or otherwise use this transmission in any manner.  If you have received this transmission in error, please alert the sender by replying to the e-mail or by contacting the sender by phone.  We also request that you immediately delete this message, and attachments, if any.  This disclaimer shall not be construed in any way to grant permission to transmit confidential information via this firm's e-mail system.

 

Statement of Confidentiality

This e-mail message, and any attachments, is confidential and is intended solely for the addressees named above.  If you are not a named recipient, an individual specifically authorized to receive this communication, or if this message has been addressed to you in error, do not read, disclose, reproduce,  or otherwise use this transmission in any manner.  If you have received this transmission in error, please alert the sender by replying to the e-mail or by contacting the sender by phone.  We also request that you immediately delete this message, and attachments, if any.  This disclaimer shall not be construed in any way to grant permission to transmit confidential information via this firm's e-mail system.

 

Statement of Confidentiality

This e-mail message, and any attachments, is confidential and is intended solely for the addressees named above.  If you are not a named recipient, an individual specifically authorized to receive this communication, or if this message has been addressed to you in error, do not read, disclose, reproduce,  or otherwise use this transmission in any manner.  If you have received this transmission in error, please alert the sender by replying to the e-mail or by contacting the sender by phone.  We also request that you immediately delete this message, and attachments, if any.  This disclaimer shall not be construed in any way to grant permission to transmit confidential information via this firm's e-mail system.