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

KRAD Client Sample App using standalone datasource instead of client

    Details

    • Similar issues:
      KULRICE-11774Create performance test environment: Standalone Server Oracle, Rice Sample App Client Oracle, KRAD Client Oracle
      KULRICE-11775Create performance test environment: Standalone Server MySQL, KRAD Client MySQL, Rice Sample App Client MySQL
      KULRICE-10632Test env for client app using standalone
      KULRICE-6749Configure rice sample app as a client app running against a standalone server
      KULRICE-12814Clean up datasource configuration
      KULRICE-13524Rice Performance Client App Double Login
      KULRICE-12596Simplify Client Spring Bean configuration
      KULRICE-6818address client app <-> standalone server implications of comparisonOperatorService
      KULRICE-13513Deploy embedded client sample app to test environment
      KULRICE-11879Split KRAD SampleApp into Client/Server mode
    • Rice Team:
      QA
    • Sprint:
      2.4.0-rc1 QA Sprint 5, 2.4.0-rc1 QA Sprint 8

      Description

      Split the KRAD Sampleapp to run as an embedded client app connected to a standalone rice server. Split the database and created two separate datasources.

      However, new travel docs created show up in standalone db instead of client db.

        Issue Links

          Activity

          Hide
          Daniel Seibert (Inactive) added a comment -

          Setting client specific alias in _KradSampleAppJpaSpringBeans.xml fixes this isssue.

          Show
          Daniel Seibert (Inactive) added a comment - Setting client specific alias in _KradSampleAppJpaSpringBeans.xml fixes this isssue.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 day, 4 hours
                1d 4h
                Remaining:
                Remaining Estimate - 1 day, 4 hours
                1d 4h
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Agile

                    Structure Helper Panel