Resolution: Cannot Reproduce
Affects Version/s: None
Fix Version/s: Not version specific
KULRICE-1779 Convert KEW Data Access Objects from OJB to JPA KULRICE-2141 Add JPA annotations and implement JPA Daos throughout Rice KULRICE-9108 Implement support for loading of both OJB and JPA versions of KRAD client-side mappings KULRICE-9066 Implement JPA version of MetadataProvider KULRICE-8923 Implement OJB version of PersistenceProvider KULRICE-8924 Implement OJB version of MetadataProvider KULRICE-9071 Implement JPA version of PersistenceProvider KULRICE-2048 Update KNS JPA DAOs to reflect changes made on 0.9.3-kfs branch by David KULRICE-9413 Implement portable data object proxy detection and unwrapping KULRICE-6014 JPA Conversion Guide
This has already been done for the KNS. However, JPA versions of KEW, KSB, KEN, KCB, KIM daos have not all been created.
Easiest way to find these is to look through the spring file for anything labeled as a DAO.
In order to continue support for both JPA and OJB, we have been using proxies to handle determining which DAO version (OJB or JPA) to use. See examples of this in the KNSSpringBeans.xml file. For example:
<bean id="persistedLookupMetadataDao" class="org.kuali.rice.kns.dao.proxy.PersistedLookupMetadataDaoProxy">
<property name="persistedLookupMetadataDaoJpa" ref="persistedLookupMetadataDaoJpa" />
<property name="persistedLookupMetadataDaoOjb" ref="persistedLookupMetadataDaoOjb" />
Essentially, what was done is to use the original OJB dao spring id for the proxy, and then rename the ojb dao spring bean to include "Ojb" at the end. Additionally, the new JPA daos have "Jpa" at the end.