[KULRICE-12421] Refactor datasource config parameter to support module specific configuration Created: 07/Apr/14  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: None
Fix Version/s: Backlog
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Major
Reporter: Eric Westfall Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relate
relates to KULRICE-9699 Database platform is currently being ... Closed
Rice Module:
Rice Core
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:
Yes

 Description   

Currently only one data source platform can be specified in rice. It would be good to allow each module have their own data source platform (e.g. KIM uses Oracle while KEW uses MySQL).

JPA doesn't require the specification of a platform, it auto-detects it. The datasource.ojb.platform looks like it's really only used for OJB configuration, in one place for display (i.e. at the top of the portal), and in common-config-defaults to control what db config gets used. The property is not used at all to determine the platform for JPA or the internal "DatabasePlatform".


Generated at Tue Oct 20 00:22:13 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.