I'm using custom deserializers on the client-side and found that I get
logged warning for missing serializers. Indeed, I don't have installed
corresponding serializers for these specific classes, because after all
they only need to be deserialized on the client-side. Or so I thought.
The stub generated by wsdl2java calls extractAttachments() close to the
end of processing an output message. Which causes, somewhere down the
calltree, a call to AttachmentsImpl#getAttachmentCount(). And that
method is implemented like this
AttachmentsImpl:
public int getAttachmentCount() {
try {
mergeinAttachments();
// force a serialization of the message so that
// any attachments will be added
soapPart.saveChanges();
return orderedAttachments.size();
} catch (AxisFault e) {
log.warn(Messages.getMessage("exception00"),e);
}
return 0;
}
Now, I don't claim to understand the code in question, but I'm pretty
sure that everything has already been serialized when it arrives on the
client-side. Another serialization-deserialization round trip should
not be necessary.
Michael
--
Michael Schuerig Cold silence has a tendency
mailto:[EMAIL PROTECTED] To atrophy any sense of compassion
http://www.schuerig.de/michael/ --Tool, Schism
