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=12685>. 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=12685 RC1 - Setting "PROP_DOMULTIREFS" looses important type info [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From [EMAIL PROTECTED] 2002-09-25 03:22 ------- I don't think this was anything recent. The relevant code seems to have been around since April or so. The deal was that ArraySerializer was explicitly (for some reason) telling the serialization system NOT to send xsi:types for array items. The intent (from the comments) seems to have been to do this IF the type matches the component type of the array, but that's not the way the code worked. Rather than fixing this in ArraySerializer (which might still want to happen) I fixed the SerializationContextImpl to notice whenever a derived type is serialized, and ALWAYS send an xsi:type. This seems the safest route to deal with all these types of problems, although there is currently a performance hit for doing so (multiple lookups). I think the find-a-serializer code could easily be modified to return both the serializer and a boolean to determine whether it is an exact match or a subtype - with that modification we'd have both accuracy and speed. That can happen post 1.0, though.
