[MGNLDMS-161] DMSUtil.addDocument() fails to remove old version of the document Created: 07/Apr/09  Updated: 03/Jul/14  Resolved: 07/Apr/09

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.3
Fix Version/s: 1.4, 1.3.1

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
relation
is related to MGNLDMS-154 Zip upload and install task: don't cr... Closed
Template:
Acceptance criteria:
Empty

 Description   

Currently when copying new version of binary assets using DMSUtil.addDocument() the old data will not be removed and new document node data will be created. This leads to old version still being shown (as only first of multiple same name siblings is considered) and size of the document is increasing.



 Comments   
Comment by Jan Haderka [ 07/Apr/09 ]

while the parent nodes are not duplicated after solving MGNLDMS-154, the DMSUtil.addDocument() still expects binary data not to be present when adding such, leading to MGNLDMS-161

Comment by Jan Haderka [ 07/Apr/09 ]

Fixed in trunk as of r25233 and on 1.3 branch as of r24242.

Generated at Mon Feb 12 00:49:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.