[KULRICE-1939] No longer possible to use KualiModule to load Data Dictionary modules after initial Data Dictionary startup Created: 29/May/08  Updated: 30/May/08  Resolved: 30/May/08

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: 0.9.3
Fix Version/s: 0.9.3

Type: Bug Fix Priority: Blocker
Reporter: Eric Westfall Assignee: Eric Westfall
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-1945Use KualiModule to load DataDictionary entries for KIM/KOM
KULRICE-12166Two instances of the data dictionary service (and data dictionary) are loaded in Rice context
KULRICE-9089Design and analysis for how new metadata and Data Dictionary will be loaded and split from current data dictionary
KULRICE-10047CollectionGroup.readOnly=true is not respected after data dictionary reload
KULRICE-3687Create data dictionary test data
KULRICE-4670integration with Data Dictionary
KULRICE-4742Look into loading of data dictionary changes to prevent full restart
KULRICE-6680UI Framework - Data Dictionary Validation
KULRICE-12564Analysis of Data Dictionary Contstraint Rewrite
KULRICE-4727Ability to specify links in data dictionary
Rice Module:
KNS
Application Requirement:
Rice

 Description   

For example, in SampleAppSpringBeans.xml we have the following:

<bean id="sampleAppModule" class="org.kuali.core.KualiModule">
<property name="moduleId" value="sa"/>
<property name="moduleName" value="Sample App"/>
<property name="moduleCode" value="sa"/>
<property name="initializeDataDictionary" value="true"/>
<property name="dataDictionaryPackages">
<list>
<value>classpath:edu/sampleu/travel/datadictionary</value>
</list>
</property>
<property name="databaseRepositoryFilePaths">
<list>
<value>OJB-repository-sampleapp.xml</value>
</list>
</property>
</bean>

It use to be the case that this would load the data dictionary files in the supplied package. It appears that this no longer happens because the DataDictionary.indexSource(...) method just adds the configuration file to a List. Since the KNS itself has already started up by the time this bean has been loaded, the actual configuration file is never loaded.



 Comments   
Comment by Eric Westfall [ 30/May/08 ]

Resolved this by calling DataDictionary.parseDataDictionaryConfigurationFiles(false) in the onEvent method of KNS Configurer on AfterStartEvent (this hooks into the Spring application context lifecycle).

Generated at Mon Jul 13 19:11:11 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.