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

Refactor datasource config parameter to support module specific configuration


    • 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?:


      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".


          Issue Links


            ewestfal Eric Westfall created issue -
            cniesen Claus Niesen made changes -
            Field Original Value New Value
            Link This issue relates to KULRICE-9699 [ KULRICE-9699 ]
            kbtaylor Kristina Taylor (Inactive) made changes -
            Rank Ranked lower
            kbtaylor Kristina Taylor (Inactive) made changes -
            Rank Ranked lower
            ewestfal Eric Westfall made changes -
            Labels Old


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


                • Created: