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

Re-examine how RiceApplicationConfigurationService is being used to resolve doc handler urls (and other variables) from across the service bus

    Details

    • Similar issues:
      KULRICE-2719Create the RiceApplicationConfigurationService for use by rice client applications
      KULRICE-5797Fix doc handler url in the AgendaEditor's doctype
      KULRICE-10085doc handler url not shown by default email stylesheet
      KULRICE-10000Re-examine design and architecture of Kuali ModuleService in terms of cleaning things up for KRAD
      KULRICE-12308Add application doc ID to doc handler URL
      KULRICE-2581doc handler urls no longer being inherited
      KULRICE-985Service Bus does not honor message.persistence property in certain situations
      KULRICE-3721The "remote" run mode for KIM (and other Rice modules?) does not allow proper consumption of services from the bus
      KULRICE-3428Review all services published from each module and determine which should be exported to the bus under which run modes (local, embedded, remote)
      KULRICE-2872Change the KEW DocumentType implementation from being an absolute URL to a relative URL using the config param 'externalizable.help.url'
    • Rice Module:
      KNS, KEW
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Currently, if KEW encounters a doc handler url of the following form:

      $

      {application.url}

      /.....

      If the document type for that document has a service namespace along the lines of something like "KFS" then it will go to the KFS application first and try and resolve application.url from the KFS application across the service bus.

      This is a good idea in theory, however for applications that have doc handler urls that don't need to call back into the application, this extra step adds extra overhead since those variables will never be resolved successfully from the client. It may also be possible in certain cases that you don't want it to resolve from the client. At the very least we need to add some caching in here to reduce the number of times we hit the service bus. Additionally, it may be worthwhile to have the RiceApplicationService have a way to provide the standalone server with information on whether or not those kinds of callbacks into the client application should be used.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 1 week
                1w
                Remaining:
                Remaining Estimate - 1 week
                1w
                Logged:
                Time Spent - Not Specified
                Not Specified

                  Structure Helper Panel