Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-12421

Refactor datasource config parameter to support module specific configuration

    Details

    • Type: Task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • 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".

        Attachments

          Issue Links

            Activity

            There are no comments yet on this issue.

              People

              • Assignee:
                Unassigned
                Reporter:
                ewestfal Eric Westfall
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: