Bug 798831 - Process inserts duplicate previous and next steps
Summary: Process inserts duplicate previous and next steps
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-01 02:40 UTC by Joshua Wulf
Modified: 2014-10-19 23:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-07 01:31:25 UTC
Embargoed:


Attachments (Terms of Use)

Description Joshua Wulf 2012-03-01 02:40:05 UTC
e.g: from the build of SPEC ID: 6192


4.3.3. Create your first Content Spec
Previous Steps in Basic Content Spec Tutorial
Section 4.3.2, “Configure csprocessor for the test server”
Section 4.3.2, “Configure csprocessor for the test server”




Result:

You now have a Content Spec for a test book with one chapter and one topic.
Next Steps in Basic Content Spec Tutorial
Section 4.3.4, “Push your first Content Spec to the server”
Section 4.3.4, “Push your first Content Spec to the server”

Comment 1 Joshua Wulf 2012-03-01 02:45:43 UTC
Spec revision: 42109

Web Service at http://csprocessor.cloud.lab.eng.bne.redhat.com:8080/ version: 0.21.4

Comment 2 Lee Newson 2012-03-05 06:37:40 UTC
Fixed in 0.22.0.

Cause:
The problem was due to a memory issue because Java stores references for Objects, I was trying to modify one object and it was modifying the same object. I was then adding the relationships twice without intentionally doing so.

Consequence:
Two relationships were being created.

Fix:
The relationships that are added are now done so that a new object that doesn't reference the old in created. This stops the duplicate relationship issue.

Comment 3 Lee Newson 2013-06-07 01:31:25 UTC
Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.


Note You need to log in before you can comment on or make changes to this bug.