[KULRICE-12814] Clean up datasource configuration Created: 10/Jun/14 Updated: 16/Jan/15
|Project:||Kuali Rice Development|
|Security Level:||Public (Public: Anyone can view)|
|Reporter:||Peter Giles (Inactive)||Assignee:||Unassigned|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|KAI Review Status:||Not Required|
|KTI Review Status:||Not Required|
|Code Review Status:||Not Required|
|Include in Release Notes?:||
There is some cleanup that needs to be done on our datasource configuration, especially with regards to KRAD.
We have three different jndi locations referenced on our project related to KRAD, and (as far as I can tell) there should only be one:
Additionally, it currently requires bean overrides to deploy our KRAD sample app as client (non-bundled), and we need to clean that up as well. Dan Seibert had to go through some hoops to get this set up in our test environments, and he shared some info on what he had to do:
override the coreConfigurer bean (which is in RiceServiceRegistrySpringBeans.xml) to
override the kradApplicationDataSource alias from _KradSampleAppJpaSpringBeans.xml to reference clientDataSource instead
We need to clean that up so that we can deploy the sample app in different vanilla configurations without resorting to bean overrides.
We will definitely need to document changes we make on our impacting changes wiki page so our customers have a heads up and can figure out how to clean their configurations up too.
|Comment by Peter Giles (Inactive) [ 10/Jun/14 ]|
I set this to blocker because it is preventing automated deployments of our sample app in non-bundled mode (there has to be a better way to say that!) for our QA environments.