Application throws Null Pointer Exception while calling web services.
0
Hi All, Following error is thrown while making web service call. I have even verified the webservice logs I did not find any logs related to xml request. I assume before creating the request it is throwing exception. can any body help in resolving the below issue. Advanced stacktrace: at com.mendix.modules.microflowengine.MicroflowUtil.processException(MicroflowUtil.java:143) Caused by: java.lang.NullPointerException: null at com.mendix.languages.mxexpressions.MxExpression.evaluate(MxExpression.scala:13) at com.mendix.integration.webservices.call.messageparts.AdvancedMessageMappingSubpart.evaluate(AdvancedMessageMappingSubpart.scala:24) at com.mendix.integration.webservices.call.messageparts.AdvancedMessagePart$$anonfun$evaluate$1.apply(AdvancedMessagePart.scala:17) at com.mendix.integration.webservices.call.messageparts.AdvancedMessagePart$$anonfun$evaluate$1.apply(AdvancedMessagePart.scala:17) at scala.collection.immutable.List.foreach(List.scala:381) at com.mendix.integration.webservices.call.messageparts.AdvancedMessagePart.evaluate(AdvancedMessagePart.scala:16) at com.mendix.integration.actions.microflow.WebServiceCallAction.createRequestInfo(WebServiceCallAction.scala:131) at com.mendix.integration.actions.microflow.WebServiceCallAction.execute(WebServiceCallAction.scala:97) at com.mendix.modules.microflowengine.microflow.impl.MicroflowObject.execute(MicroflowObject.java:47) at com.mendix.modules.microflowengine.microflow.impl.MicroflowImpl.executeAfterBreakingIfNecessary(MicroflowImpl.java:192)
asked
Ramesh Kshirsagar
3 answers
0
It seems to go wrong in mapping a sub part of your mapping, perhaps an input parameter is not filled or a mapping is not set. That being said this does seem like a bug in the mendix framework perhaps updating your modeler will give you a better error message.
answered
Pieter van de Braak
0
Thank you very much.
It worked in upgraded version. But not sure what is causing the issue in 6.9.0 version.
Need to figure out.
answered
Ramesh Kshirsagar
0
Solution: There is an additional optional element in the schema besides header and body in the message request which is causing above error in 6.9.0 version. It worked after removing it.