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

Create a rice-sample-applications repository in SVN and update sample embedded and thin client examples from 0.9.2/0.9.3 and put them in there


    • Similar issues:
      KULRICE-2933Check in recipe_reference application into Rice sample applications SVN repository
      KULRICE-4545Update Sample Embedded Client
      KULRICE-4392Update sample applications to latest version of rice
      KULRICE-2817Deploy thin client sample app to test environment
      KULRICE-4902Rice Thin Client Refactor
      KULRICE-13513Deploy embedded client sample app to test environment
      KULRICE-13102Production Move of svn to git
      KULRICE-3783Reduce client-side library dependencies for KEW thin client applications
      KULRICE-4795Create sample travel app that uses war overlays and embedded mode
      KULRICE-6749Configure rice sample app as a client app running against a standalone server
    • Rice Team:


      We need to update our existing sample applications to validate that there aren't any issues in Rice 1.0 with configuration. There are some existing sample clients that we can work with at the following location:


      We should first create a new svn repository called rice-sample-applications (will need to work with Farooq or Eric on this)

      Then create a branch under this called "rice-release-1-0-0-br"

      Then we should copy the existing sample clients into it and update them for Rice 1.0. Initially i'm mostly concerned with the embedded client application and the thin client application initially.

      As part of this process we need to create documentation on:

      1) How to configure an embedded Rice client - this should be written from the perspective of creating an embedded rice application that points to a standalone server database where the application and the standalone rice server databases are separate.
      2) How to configure a thin Rice client - in this case we are referring to a Rice application that uses thin client integration (direct service calls, no embedded workflow engine) to communicate with the Rice standalone server

      We will want to take note of any bugs in this setup, it's different than how our sample application and how KFS development environment works.

        Issue Links



            • Assignee:
              Peter Giles (Inactive)
              Eric Westfall
            • Votes:
              0 Vote for this issue
              3 Start watching this issue


              • Created:

                Time Tracking

                Original Estimate - 1 week
                Remaining Estimate - 1 week
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel