AnsweredAssumed Answered

request.mainpart is null

Question asked by richiethom on Sep 12, 2016
Latest reply on Jan 10, 2019 by Cristian.garcia



I am trying to fix a problem with a webservice that is supposed to work with a multipart message. For some reason only one of our clients is having this problem, for everyone else it is working correctly.


By adding the debugger to the service, we have been able to see that the API Gateway is unable to extract any data from the request and populate request.mainpart, even though we are sure that there is data there. This in turn causes sebsequent assertions to fail.


The Content-Type for this request is


"multipart/related; type="text/xml"; boundary="...""


Having seen a question here about response.mainpart being null, we have tried the approach suggeested in that answer, and have added the following variables to the debugger:




With these variables in the debugger, we have obtained the following values:

request.mainpart = null = null = null[0] = {j} "com.l7tech.common.mime.j@1d3937c6"

the class 'j' is obviously an obfuscated Java class, but we are unsure what to do with it.


Any help or pointers would be greatly appreciated.


Kind regards


Richard Thomas