[
https://issues.apache.org/jira/browse/OFBIZ-9981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469968#comment-16469968 ]
Suraj Khurana commented on OFBIZ-9981:
--------------------------------------
Hello,
It is observed that from developer perspective, sometimes becomes difficult to trace the exact module from which error has returned by reading logs.
*Proposed solution*: It would be good if we could have another constructor of _returnProblem_ having module as parameter as well so that we can trace for exactly which module service has returned error.
Thoughts !!
> Handle service response effectively
> -----------------------------------
>
> Key: OFBIZ-9981
> URL:
https://issues.apache.org/jira/browse/OFBIZ-9981> Project: OFBiz
> Issue Type: Improvement
> Reporter: Suraj Khurana
> Assignee: Jacques Le Roux
> Priority: Major
> Attachments: OFBIZ-9981-MAR-SECEXT-WE.patch, OFBIZ-9981-content.patch, OFBIZ-9981-manufacturing.patch, OFBIZ-9981-order.patch, OFBIZ-9981-party.patch, OFBIZ-9981-plugins.patch, OFBIZ-9981-product.patch, OFBIZ-9981.patch
>
>
> [As per discussion on Dev ML|
http://markmail.org/message/dfriai337uxlx5mo]:
> ==========================
> Every service calling from java/groovy must handle errors by service util methods such as isError, reutrnError etc. and similarly in case of XML <call-service, there should be <check-error/> to make sure service was executed successfully.
> Apart from this, one suggestion is to include *Debug.logError* in *_ServiceUtil.returnProblem_* so that in case of any error occurred and handled, it will always be logged on the console.
> ==========================
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
