[AXIOM-181] Exception thrown is not descriptive, if content-type missing boundary parameter

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.8
• Assignee: Andreas Veithen
• Reporter: Michael Kaye
• Created: 18/Sep/08 18:44
• Updated: 27/Mar/11 11:42
• Resolved: 07/Dec/08 15:06

Description

Looking at org.apache.axiom.attachments.Attachments, if the contentType supplied is something like:

contentType="multipart/mixed;boundary=BOUNDARY"

then the value of this.boundary will be "--BOUNDARY".getBytes();

contentType="multipart/mixed"

then the value of this.boundary will be "--null".getBytes();

This will cause the parser to skip the entire stream and a :
throw new OMException("Mime parts not found. Stream ended while searching for the boundary"); exception will be thrown.

It would be useful if the code checked for a null boundary and threw a more descriptive error – the issue is not that the stream ended prematurely, nor that there was no boundary, but that the boundary parameter was missing from the ContentType.

This applies against 1.2.5 and 1.2.6