[WINK-371] Data conversion issue for Multi-part MIME on mainframe (z/OS)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2
• Component/s: Server

Environment

z/OS primarily

• Assignee: Unassigned
• Reporter: Peter Masters
• Created: 31/Oct/12 14:47
• Updated: 15/Mar/15 06:13
• Resolved: 15/Mar/15 06:13

Description

We have a method annotated as follows:-

@POST
@Consumes(MediaType.MULTIPART_FORM_DATA)
@Produces(MediaType.TEXT_XML)

When we look through the parts on zOS, using:
while (iterator.hasNext())

{ InPart part = iterator.next(); InputStream is = part.getBody(InputStream.class, null); ... }

we see an exception
java.lang.StringIndexOutOfBoundsException
at java.lang.String.substring(String.java:1092)
at org.apache.wink.common.internal.providers.multipart.MultiPartParser.parseHeaders(MultiPartParser.java:264)
at org.apache.wink.common.internal.providers.multipart.MultiPartParser.nextPart(MultiPartParser.java:109)
at org.apache.wink.common.model.multipart.InMultiPart.hasNext(InMultiPart.java:83)
...

The headers going over the wire are in UTF-8, but I believe Wink is trying to decode them as platform encoding (e.g. a new String(bytes), without a codepage specified). On a regular windows/linux box this would work for normal codepoints, but on zOS, EBCDIC encoding is nothing like UTF-8, so the assumption wouldn't work. I'm unfortunately not permitted to look at wink sourcecode (legal reasons) so I cannot verify this myself, but as this is a string handling error on a UTF-8 string, that is the best guess I can do.