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

Externalizable BO lookups and inquiries don't work with standalone Rice

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.1.1
    • Fix Version/s: KFS Release 4.0, 1.0.3
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-6446Links in lookup results don't function in IE8
      KULRICE-6045Add coverage of Externalizable Business Objects to Rice docs
      KULRICE-6993KNS Infrastructure not supporting quickfinder lookups against standalone Rice server
      KULRICE-3099Doc header person inquiry may not work w/standalone rice server
      KULRICE-9899Add documentation to IG on how to configure an application to work with Rice standalone server
      KULRICE-6506Better Fix: Links in lookup results don't function in IE8
      KULRICE-4576Looks like there is a bug in the KNS framework with nested collections and externalizable business objects.
      KULRICE-3423in Parameter Lookup, the Component field direct inquiry doesn't work
      KULRICE-2855Document Kuali Rice Standalone Server installation and configuration
      KULRICE-2895All inquiry links in Rice standalone are incorrect
    • Rice Module:
      KNS
    • Application Requirement:
      KFS, Rice

      Description

      Externalizable BOs incorrectly use the "kr.url" property when generating their lookup and inquiry links. When running Rice standalone, this variable refers to the /kr path on the Rice server, not the client application which can handle those business objects.

      The links should be constructed using $

      {application.url}

      /kr instead.

      Also fixed another location using kr.url to render help links. These should go to the calling server, not always to the rice server.

      See patch.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          Jonathan, do you want to go ahead and apply this patch to either 1.0.3 or 1.0.2.1?

          Show
          Eric Westfall added a comment - Jonathan, do you want to go ahead and apply this patch to either 1.0.3 or 1.0.2.1?
          Hide
          Jonathan Keller added a comment -

          Sure. I'll do 1.0.3 based on our recent discussions. The only question would be if the KC team wants it for their release.

          Actually, for fundamental issues like this that could affect multiple projects, I'm inclined to put it in the soonest patch release.

          So - I'll apply it to 1.0.2.1 so KC can have the fix as well. We don't need it for day-to-day development and testing, so it can wait until we merge in 1.0.2.1 to 1.0.3.

          Show
          Jonathan Keller added a comment - Sure. I'll do 1.0.3 based on our recent discussions. The only question would be if the KC team wants it for their release. Actually, for fundamental issues like this that could affect multiple projects, I'm inclined to put it in the soonest patch release. So - I'll apply it to 1.0.2.1 so KC can have the fix as well. We don't need it for day-to-day development and testing, so it can wait until we merge in 1.0.2.1 to 1.0.3.
          Hide
          Eric Westfall added a comment -

          Jonathan, can you ask KC about this in the next KTI? Thanks!

          Show
          Eric Westfall added a comment - Jonathan, can you ask KC about this in the next KTI? Thanks!

            People

            • Assignee:
              Jonathan Keller
              Reporter:
              Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel