[
https://issues.apache.org/jira/browse/OFBIZ-8722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15643288#comment-15643288 ]
Rishi Solanki commented on OFBIZ-8722:
--------------------------------------
I would say, the fix designed for the problem reported here is not appropriate and it is tightly coupled for certain scenario, which can not be handled by the user of the service. A service should be enough flexible which will give option user on how to use it. Before applying the fix as a user I will have option to get the records on PKs and change the non PK as per my requirement. After this change user always requires to put some values in the service parameters.
IMO it is violating the loose coupling. We should rethink on weather the reported problem was really a problem? and if so then on solution provided for this?
> Update Services set non-pk fields to null, if only passed pks
> -------------------------------------------------------------
>
> Key: OFBIZ-8722
> URL:
https://issues.apache.org/jira/browse/OFBIZ-8722> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Pawan Verma
> Assignee: Rishi Solanki
>
> When we pass only pks in some update services. All non-pk values are getting null.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
