Details

    • Type: Task Task
    • Status: Open Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.6
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Similar issues:
      KULRICE-11046classpath:org/kuali/rice/config/rice-krad-sampleapp-config.xml does not exist on krad-sampleapp deploy
      KULRICE-11142Reloading Data Dictionary Error:(13,1 ) you tried to assign a value to the class 'config'. Do you have a script with this name?
      KULRICE-9369Upgrade Script Error
      KULRICE-9934Create a config parameter for date constraint text to display to user in KRAD
      KULRICE-2093Remove Error Handling properties from config files that should instead be in Spring
      KULRICE-11102KRAD JS Lookup Error
      KULRICE-12187KRAD SampleApp Client startup errors
      KULRICE-11105KRAD JS Error in Rice 2.4.0-M3
      KULRICE-10188separate config options for controlling performance and minification options instead of rice.krad.dev.mode
      KULRICE-5468Rice Dev: KRAD breadcrumbs Home throws error
    • Rice Module:
      Rice Core
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      There is a bug in the client data source jpa spring bean configuration.
      It only reveals itself when attempting to run the KRAD Sample App in client / server mode.

      The symptoms are that in a client/server deployment (with kim.mode and kew.mode both set to EMBEDDED),
      Krad Client Documents, such as the Travel related maintenance documents in the KRAD samplapp Demo section, are created and persisted in the Rice standalone server database instead of the client database.

      In file _KradSampleAppJpaSpringBeans.xml, an alias is defined named "clientDataSource".
      The value of the alias is erroneously set to to "riceDataSource" which is the server data source instead of the client data source. This should be changed to point to a client data source alias (if one exists, it it doesn't exists one should be made).

      Then for bundled mode configurations, the client and server aliases should both be set to point to the same data source.

        Issue Links

          Activity

          Hide
          Daniel Seibert (Inactive) added a comment -

          This bug was originally included as part of KULRICE-12596

          Show
          Daniel Seibert (Inactive) added a comment - This bug was originally included as part of KULRICE-12596

            People

            • Assignee:
              Unassigned
              Reporter:
              Daniel Seibert (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Structure Helper Panel