Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0025773Openbravo ERPA. Platformpublic2014-02-19 18:102014-03-03 10:00
caristu 
alostale 
immediateminoralways
closedfixed 
5
3.0MP28.5 
3.0PR14Q2 
shankarb
Core
Production - Confirmed Stable
2013-07-19
https://code.openbravo.com/erp/devel/pi/rev/7d6d644b9b9e3b9ca55c7be357af7bb86a257263 [^]
No
0025773: Error thrown in web services if the request includes a field that references a computed column
The following error is thrown when trying to create a new business entity and if we include in the request a field that references a computed column (attached is an example):

<ob:error xmlns:ob="http://www.openbravo.com"><message>org.openbravo.service.web.InvalidContentException: [^] Exception when parsing entity MaterialMgmtShipmentInOut (null):null
Caused by: Exception when parsing entity EntityName (null):null</message></ob:error>

In description
No tags attached.
duplicate of design defect 00241043.0MP27 closed alostale Unnecessary evaluation of computed columns 
related to defect 0025862 closed alostale get_computedColumns() method returns null under some circumstances 
related to defect 0036624 closed platform Error thrown in web services if the URL includes a where parameter that references a computed column 
xml ws.xml (2,605) 2014-02-19 18:12
https://issues.openbravo.com/file_download.php?file_id=6713&type=bug
Issue History
2014-02-19 18:10caristuNew Issue
2014-02-19 18:10caristuAssigned To => AugustoMauch
2014-02-19 18:10caristuModules => Core
2014-02-19 18:10caristuTriggers an Emergency Pack => No
2014-02-19 18:10caristuRegression level => Production - Confirmed Stable
2014-02-19 18:11caristuIssue Monitored: networkb
2014-02-19 18:12caristuFile Added: ws.xml
2014-02-19 18:13caristuversion3.0MP30.3 => 3.0MP28.5
2014-02-20 15:45alostaleAssigned ToAugustoMauch => alostale
2014-02-20 17:19alostaleReview Assigned To => shankarb
2014-02-20 17:20hgbotCheckin
2014-02-20 17:20hgbotNote Added: 0064457
2014-02-20 17:20hgbotStatusnew => resolved
2014-02-20 17:20hgbotResolutionopen => fixed
2014-02-20 17:20hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/ac5a01fde1a7b212090eec0fae96562b6f24d806 [^]
2014-02-21 00:45hudsonbotCheckin
2014-02-21 00:45hudsonbotNote Added: 0064470
2014-02-21 08:57hgbotCheckin
2014-02-21 08:57hgbotNote Added: 0064471
2014-02-21 08:59alostaleNote Added: 0064472
2014-02-21 16:27dmitry_mezentsevNote Added: 0064495
2014-02-21 16:28hudsonbotCheckin
2014-02-21 16:28hudsonbotNote Added: 0064498
2014-02-21 16:52alostaleStatusresolved => new
2014-02-21 16:52alostaleResolutionfixed => open
2014-02-21 16:53alostaleRegression date => 2013-07-19
2014-02-21 16:53alostaleRegression introduced by commit => https://code.openbravo.com/erp/devel/pi/rev/7d6d644b9b9e3b9ca55c7be357af7bb86a257263 [^]
2014-02-21 16:53alostaleStatusnew => scheduled
2014-02-21 16:53alostalefix_in_branch => pi
2014-02-21 16:53alostaleStatusscheduled => resolved
2014-02-21 16:53alostaleResolutionopen => fixed
2014-02-21 16:54alostaleNote Added: 0064501
2014-02-25 14:03shankarbNote Added: 0064564
2014-02-25 14:03shankarbStatusresolved => closed
2014-02-25 14:03shankarbFixed in Version => 3.0MP32
2014-03-03 09:57alostaleStatusclosed => new
2014-03-03 09:57alostaleResolutionfixed => open
2014-03-03 09:58alostaleFixed in Version3.0MP32 =>
2014-03-03 09:58alostaleRelationship addedrelated to 0025862
2014-03-03 09:59alostaleRelationship addedduplicate of 0024104
2014-03-03 09:59alostaleNote Added: 0064711
2014-03-03 09:59alostaleSeveritymajor => minor
2014-03-03 09:59alostalefix_in_branchpi =>
2014-03-03 10:00alostaleStatusnew => scheduled
2014-03-03 10:00alostalefix_in_branch => pi
2014-03-03 10:00alostaleStatusscheduled => resolved
2014-03-03 10:00alostaleResolutionopen => fixed
2014-03-03 10:00alostaleStatusresolved => closed
2014-03-03 10:00alostaleFixed in Version => 3.0MP32
2017-08-08 11:28JONHMRelationship addedrelated to 0036624

Notes
(0064457)
hgbot   
2014-02-20 17:20   
Repository: erp/devel/pi
Changeset: ac5a01fde1a7b212090eec0fae96562b6f24d806
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Thu Feb 20 17:19:02 2014 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/ac5a01fde1a7b212090eec0fae96562b6f24d806 [^]

fixed bug 25773: error in xml REST ws when adding a row with a computed column

---
M src/org/openbravo/dal/xml/XMLEntityConverter.java
---
(0064470)
hudsonbot   
2014-02-21 00:45   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/75835cd7cac8 [^]
Maturity status: Test
(0064471)
hgbot   
2014-02-21 08:57   
Repository: erp/devel/pi
Changeset: ec0c56f1c84757693a4eabcaf5f61c6c4cc8a1d8
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Fri Feb 21 08:56:43 2014 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/ec0c56f1c84757693a4eabcaf5f61c6c4cc8a1d8 [^]

related to issue 25773: added test cases to cover the issue using XML and JSON

---
M src-test/org/openbravo/test/AllWebserviceTests.java
M src-test/org/openbravo/test/webservice/BaseWSTest.java
A src-test/org/openbravo/test/webservice/WSAddRecordWithComputedColumns.java
---
(0064472)
alostale   
2014-02-21 08:59   
Test plan: check it is possible to insert records that include computed columns in their request content using both XML and JSON web services.

Test plan automatized using jUnit: src-test/org/openbravo/test/webservice/WSAddRecordWithComputedColumns.java
(0064495)
dmitry_mezentsev   
2014-02-21 16:27   
Asier,

Could you update Regression fields please?
(0064498)
hudsonbot   
2014-02-21 16:28   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/b309487a3fb6 [^]
Maturity status: Test
(0064501)
alostale   
2014-02-21 16:54   
Regression present since mp27
(0064564)
shankarb   
2014-02-25 14:03   
Code reviewed and tested in pi changeset 7feaacbc88b1.
(0064711)
alostale   
2014-03-03 09:59   
Downgraded severity to minor:

The walkaround to this issue would be not including in the property field in the XML. It does not make any sense to include them in PUT/POST operations, because all property fields are read only.