DO NOT REPLY [Bug 15148] New: - test.wsdl.attachments test error is masked

[bugzilla]

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=15148>.
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=15148

test.wsdl.attachments test error is masked

           Summary: test.wsdl.attachments test error is masked
           Product: Axis
           Version: 1.1beta
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Serialization/Deserialization
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


In encoding.ser.MimeMultipartDataHandlerDeserializer.java, line 95 an error is 
thrown from the javax.mail.internet.MimeMultipart class (method mmp.getCount()) 
when the attachment test is executed.  We used to swallow these errors, Glen 
changed the code to throw a SAXException, and I just changed the code to set 
the value of the Deserialized object to be null and continue.

This is masking the real problem, which I am unable to uncover, since I know 
very little about how the Axis attachment support works.

I have commented the code with a FIXME, here is what it looks like now:
        if (getValue() instanceof DataHandler) {
            try {
                DataHandler dh = (DataHandler) getValue();
                MimeMultipart mmp = new MimeMultipart(dh.getDataSource());
                if (mmp.getCount() == 0) {
                    mmp = null;
                }
                setValue(mmp);
            }
            catch (Exception e) {
                // FIXME - we need to propigate these errors, but this breaks
                // the test.wsdl/attachments multi-part tests, which pass
                // empty stuff over the wire, which seems to screw up the
                // MimeMultipart class.  Why did this ever work?
                // throw new SAXException(e);
                setValue(null);
            }
        }