Implemented a performance improvement by fetching data directly from the database instead of using the report layer.

This change is included in patch version *4.0.0.8*.

Perf Issue

Working, but getting Performance issue now : 1.2s versus 21s

it works try below request :

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ser="http://server.internal.api.srd.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:checkMwOrGeFeasibility>
<requestId>646</requestId>
<serviceName>1291106_MPLS</serviceName>
<siteLat>19.529411</siteLat>
<siteLong>57.6157</siteLong>
<maxDistanceInMeters>50000</maxDistanceInMeters>
<coordinateFormat>geo_wgs84</coordinateFormat>
<bandWith>10</bandWith>
<nbLines>1</nbLines>
<nbChannels>1</nbChannels>
</ser:checkMwOrGeFeasibility>
</soapenv:Body>
</soapenv:Envelope>

API : checkMwOrGeFeasibility
Please support to prepare the input of this API as the current one is showing error

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://server.internal.api.srd.nep.mobinets.com/">
<soapenv:Header/>
<soapenv:Body>
<ser:checkMwOrGeFeasibility>
<!-Optional:->
<requestId>821</requestId>
<!-Optional:->
<serviceName>1319442_FBB</serviceName>
<!-Optional:->
<siteLat>23.55626893321905</siteLat>
<!-Optional:->
<siteLong>58.21754375406719</siteLong>
<!-Optional:->
<maxDistanceInMeters>30.0</maxDistanceInMeters>
<!-Optional:->
<coordinateFormat>geo_wgs84</coordinateFormat>
<!-Optional:->
<bandWith>10</bandWith>
<!-Optional:->

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>eq(null) is not allowed. Use isNull() instead</faultstring>
<detail>
<ns1:NepFault xmlns:ns1="http://server.internal.api.srd.nep.mobinets.com/">
<errorCode xmlns:ns2="http://server.internal.api.srd.nep.mobinets.com/">-1</errorCode>
</ns1:NepFault>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
<nbLines>10</nbLines>
<!-Optional:->
<nbChannels>10</nbChannels>
</ser:checkMwOrGeFeasibility>
</soapenv:Body>
</soapenv:Envelope>

fix will be available with release 4.0.0.5

check if customer name is null before using eq method of QueryDSL