axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15369] - Interface Serializer/Deserializer needed!!
Date Mon, 17 Feb 2003 18:23:50 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15369>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15369

Interface Serializer/Deserializer needed!!

gdaniels@macromedia.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From gdaniels@macromedia.com  2003-02-17 18:23 -------
When the serialization system gets to a given object, it looks for the most 
exact match for that object's class when finding a Serializer.  So if you've 
registered a Serializer for MyRequest, that's the one you'll get.  You could 
ALSO register a "Request" interface serializer, which would only get the 
information available from the Request API in doing its work, for serializing 
generic Request objects.  So I don't think this is a valid enhancement, since 
I don't see that it's anything new.

(If what you're looking for is the ability to do custom serialization on a 
class WITHOUT registering that class explicitly in the TypeMapping system, we 
have that too - we look for an optional getSerializer()/getDeserializer() 
static method on the class object.)

Mime
View raw message