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

Create the RiceApplicationConfigurationService for use by rice client applications

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-2695Create 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
      KULRICE-6021Identify and document where the Rice standalone server can make calls back into client applications
      KULRICE-1758Find ways to reduce client application library dependencies in Rice
      KULRICE-4451Re-examine how RiceApplicationConfigurationService is being used to resolve doc handler urls (and other variables) from across the service bus
      KULRICE-13524Rice Performance Client App Double Login
      KULRICE-4495Identify locations where client applications are allowed to connect and use the Rice standalone server database
      KULRICE-3950Allow KNS-enabled client applications to run KEW in "remote" mode.
      KULRICE-2768Update ParameterService to allow for it to query all Rice client applications for their components
      KULRICE-13134Create Rice 2.5 environments for testing client/server deployments
      KULRICE-13348KRAD Client Sample App using standalone datasource instead of client
    • Application Requirement:
      KFS, Rice

      Description

      See linked issue:

      A standalone rice server will need to obtain some information from the client applications which are connected to its workflow engine. The primary use case for this at the moment is the $

      {application.url}

      variable in the document handlers.

      Add applicationNamespaceCode to the rice namespace table. If there's a UI/maintenance document for this table, add the new field to those as well.

      Create the service interface with a method:
      getConfigurationParameter( String parameterName ) - the default implementation can just return the parameter value from the KualiConfigurationService

      Add this service implementation to the KNSSpringBeans.xml file

      In KEW, when doc handler URLs are being resolved: (Eric, are there other places?)
      use the serviceNamespace on the document type to determine which instance of the service to pull off the bus. Use the ResourceLocator (GlobalResourceLoader?) to pull the "riceApplicationConfigurationService" from the service bus with the namespace from the document type.

        Issue Links

          Activity

          Hide
          Jonathan Keller added a comment -

          Yes - there is another place where we will want this service to be called for properties:

          The KIM Type Services when they are returning the URLs for the lookups and inquiries need to call this service. They will need to pull the applicationNamespaceCode off the namespace table for the namespace of the component which is being asked for.

          E.g. - if the BO Object is Account, call the KualiModuleService.getResponsibleModule( Account.class )
          From that, get the namespace code and use that to get the applicationNamespaceCode.
          That can be used when making a call to GlobalResourceLoader.getService( QName ) to obtain the DD service from KFS over the service bus.

          Show
          Jonathan Keller added a comment - Yes - there is another place where we will want this service to be called for properties: The KIM Type Services when they are returning the URLs for the lookups and inquiries need to call this service. They will need to pull the applicationNamespaceCode off the namespace table for the namespace of the component which is being asked for. E.g. - if the BO Object is Account, call the KualiModuleService.getResponsibleModule( Account.class ) From that, get the namespace code and use that to get the applicationNamespaceCode. That can be used when making a call to GlobalResourceLoader.getService( QName ) to obtain the DD service from KFS over the service bus.
          Hide
          Eric Westfall added a comment -

          The main place this happens from a KEW perspective is in Utilities.substituteConfigParameters which eventually calls out to the ConfigStringLookup class.

          Show
          Eric Westfall added a comment - The main place this happens from a KEW perspective is in Utilities.substituteConfigParameters which eventually calls out to the ConfigStringLookup class.
          Hide
          Eric Westfall added a comment -

          Bulk change of all Rice 1.0 issues to closed after public release.

          Show
          Eric Westfall added a comment - Bulk change of all Rice 1.0 issues to closed after public release.

            People

            • Assignee:
              Jean Zhou (Inactive)
              Reporter:
              Jonathan Keller
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel