[KULRICE-11468] Add ability to remove mappings from superclass with JPA Created: 17/Dec/13  Updated: 21/Apr/14  Resolved: 17/Dec/13

Status: Closed
Project: Kuali Rice Development
Component/s: Development, JPA
Affects Version/s: None
Fix Version/s: 2.4
Security Level: Public (Public: Anyone can view)

Type: New Feature Priority: Critical
Reporter: Eric Westfall Assignee: Eric Westfall
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 1 hour
Time Spent: Not Specified
Original Estimate: 1 hour

Similar issues:
KULRICE-7636Remove requirement that baseDocumentClass is a superclass of the documentClass
KULRICE-13135Remove all membership mappings from GroupBo and RoleBo
KULRICE-11148JPA mapped transactional document fields not linking
KULRICE-6014JPA Conversion Guide
KULRICE-11496Convert KCB entities from OJB to JPA
KULRICE-2358Remove DTYPE column from Rice tables
KULRICE-10866Modify the KradEclipseLinkCustomizer so that the @PortableSequenceGenerator annotation can be placed on a superclass field
KULRICE-10107Remove array and map initializing from component constructors
KULRICE-2141Add JPA annotations and implement JPA Daos throughout Rice
KULRICE-12710Add ability to define the text for required for next state indicator
Sprint: 2.4.0-m3 JPA Sprint 4
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:


Create @RemoveMappings and @RemoveMapping annotations which take an attribute name and allow for mappings to be "unmapped" from a superclass.

Comment by Eric Westfall [ 17/Dec/13 ]

This has been completed and checked into the project.

Generated at Sat Jun 06 03:06:11 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.