Because I want to filter the properties being marshalled to the client -- I've handled it anyway via the concept of a "NullDeserializer".
Cory -----Original Message----- From: Mark Galbreath [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2003 4:46 PM To: [EMAIL PROTECTED] Subject: RE: serialize but not deserialize Why are you using custom de/serializers? All you have to do is fool Axis into believing the class to be transformed is a JavaBean. Mark -----Original Message----- From: Cory Wilkerson [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 11, 2003 3:55 PM There are cases when I'll need to serialize an element to a consumer but never have to deserialize that same element. Using custom serializers and deserializers, it appears as though I'm forced to provide factories that at the very least will return dummy representations of deserializers so that typeMapping deployments work correctly. Am I missing anything here or is this the way it has to be? Thanks, Cory
