Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-12421

Refactor datasource config parameter to support module specific configuration

    Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Backlog
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-4461Implement config-coded-defaults.xml support for Rice JPA datasource properties
      KULRICE-2878Remove configuration parameter constants from Config onto appropriate constants classes
      KULRICE-12310Add dataSource property to CoreServiceConfigurer
      KULRICE-12814Clean up datasource configuration
      KULRICE-5098Create krms module configuration
      KULRICE-1747Ordering of config parameters and nested configs is not respected
      KULRICE-2790Split Rice datasource configuration for KNS datasources across client-side and server-side
      KULRICE-4190Implement a better way for KNS client apps running Rice modules in 'remote' run mode to set the various Rice module xxx.url parameters like kew.url, kim.url, etc.
      KULRICE-3761Refactor XPathQualifierResolver so that it may also be used as a Role route node/module
      KULRICE-20Configuration needs to support swapping between JNDI and Spring based datasources
    • 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".

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

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

              Dates

              • Created:
                Updated:

                Structure Helper Panel