Bug 780223 (SOA-2610) - When A File Node Is Removed The Associated Sequenced Nodes Should Also Be Removed
Summary: When A File Node Is Removed The Associated Sequenced Nodes Should Also Be Rem...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-2610
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: EDS
Version: 5.1.0.ER4
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.1.0.CR1
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-24 15:24 UTC by Van Halbert
Modified: 2011-02-04 20:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-04 20:37:42 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-2610 0 None None None Never

Description Van Halbert 2010-11-24 15:24:51 UTC 
project_key: SOA

When a file is published/uploaded to a repository a file node is created. Also, other nodes may be created due to sequencing. Yet, when that file node is removed the nodes created by the sequencers are not deleted and should be.
Comment 1 Van Halbert 2010-11-24 15:24:52 UTC 
Link: Added: This issue Cloned from MODE-1028
Comment 2 Van Halbert 2010-11-24 15:25:18 UTC 
Security: Added: Public
Comment 3 Randall Hauch 2010-12-22 18:48:48 UTC 
MODE-1028 has just been marked as resolved, since the new feature was just committed to trunk and to the '2.2.x' branch (used for SOA-P 5.1.0 GA).
Comment 5 Van Halbert 2011-02-04 20:37:42 UTC 
This has been fixed in the project and verified.
Note You need to log in before you can comment on or make changes to this bug.