Build full Role maintenance document (KULRICE-1672)
[KULRICE-1920] Ensure collection deletions work for all KIM collections
Created: 21/May/08 Updated: 01/Jul/08 Due: 27/Jun/08 Resolved: 01/Jul/08
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Issue Links:
Similar issues:
Closed
Kuali Rice Development
Development
None
0.9.3
Sub Task
Aaron Godert (Inactive)
Fixed
None
Not Specified
Priority:
Assignee:
Votes:
Blocker
Nirmal JosephSahaya (Inactive)
0
Not Specified
Not Specified
Relate
is related
to
KULRICE1962
KULRICE-5328
Enhance Maintenance Document
framewor...
Closed
Collection delete is not working for updateable
references.
KULRICE-5036 Develop proposition that works with collections
KULRICE-9463 Kim authorization configuration not working for
groups inside stacked collection
KULRICE-2070 Sub-collection deletions not working properly
KULRICE-1900 Problems deleting collection items in maintenance
documents
KULRICE-12034 Delete creating blank rows in Component Library /
Collections / Sequence Column
KULRICE-4723 Better collection layout support
KULRICE-7675 Collection Search doesn't work
KULRICE-3223 Ensure that collection-based results returned from
CacheNoCopy methods are unmodifiable
KULRICE-7379 Bug with Sub-collection in KNS L&F related to
shading on hover
Rice Module:
Application
Requirement:
KIM
Rice
Description
See Chris's sample in the Group class and DD files.
Comments
Comment by Chris Kirschenman (Inactive) [ 24/Jun/08 ]
we should be able to get rid of that hack KIM base class now that my maintenance changes are
in. I only did the change to Group as a proof of concepts but for the other documents all that has
to be done is to add:
<property name="alwaysAllowCollectionDeletion" value="true" />
to each of the collection in the maintenance dd files. You could probably repurpose this jira to
handle that task (deleting the base class and adding that attribute to all the files) and give it to
Nirmal or another dev. It shouldn't take long at all. The only time consuming part is bringing up
and submitting each doc for testing.
Comment by Aaron Godert (Inactive) [ 27/Jun/08 ]
Cool, just saw this. I can re purpose and give to Nirmal.
Comment by Aaron Godert (Inactive) [ 27/Jun/08 ]
Nirmal, please take a look at this one today.
Chris can show you what has to get done. Since I'll be working with the Entity document, I'll
handle that one.
In addition to adding this new property to all collections, you'll need to get rid of the hack that
we put in place for the temporary fix.
Thanks,
AG
Comment by Chris Kirschenman (Inactive) [ 27/Jun/08 ]
Nirmal let me know if you have any questions.
Steps to do:
1. For each maintenance doc that has a collection open the DD and add the above property to the
collections
2. Change the class that the java file is inheriting from KIMPersistableBusinessObjectBase to
PersistableBusinessObjectBase
3. Test the maintenance doc to make sure the delete appears throughout the lifecycle (not just
after adding)
4. When finished check for references to KIMPersistableBusinessObjectBase, if you've got
them all delete that file.
You can see Group for an example.
Thanks
Comment by Nirmal JosephSahaya (Inactive) [ 27/Jun/08 ]
thanks Chris, I will do and let you know If I have any questions
Comment by Nirmal JosephSahaya (Inactive) [ 01/Jul/08 ]
This is done and tested, the KIMPersistableBusinessObjectBase file has been deleted
Comment by Aaron Godert (Inactive) [ 01/Jul/08 ]
Thanks Nirmal. I'm closing this out.
Generated at Tue Feb 09 14:03:08 CST 2016 using JIRA 6.1.5#6160sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.