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

Improve how "store-and-forward" services are implemented in respect to the service registry

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: Not version specific
    • Component/s: Development
    • Labels:
      None
    • Similar issues:
      KULRICE-4511Refactor service registry to implement inclusion of version numbers in the service registry
      KULRICE-2346Improve how the KSB handles "dead" services
      KULRICE-206Implement "store and forward" in KEW
      KULRICE-4816Implement interaction with the service registry so that it goes over remote connection instead of direct database access
      KULRICE-509Implement Store and Forward cability for KSB
      KULRICE-13852Implement the capability for applications integrated with the KSB service registry to startup even if the registry is offline
      KULRICE-8327Implement caching for Message Service
      KULRICE-4409Add Ability to delete 'localhost' entries in Service Registry from Interface
      KULRICE-12279Make KSBConfigurer handle if web service call fails to remote service registry
      KULRICE-4894Duplicate entries in the service registry
    • Rice Module:
      KSB
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Currently, in order for "store-and-forward" capabilities to work in the KSB, all services end up getting published a second time with "-forwardHandler" tacked onto the end of the name. This is very hackish and as part of Rice 1.1 we need to maintain compatibility for all service endpoints moving forward so it would be good to clean this up.

      A couple of ideas here include implementing some sort of "message broker" service which all messages are "forwarded" to as part of a store and forward scheme.

      Furthermore, if we have time it would be good to improve how store and forward works in Rice. Currently it's an all or nothing configuration for the client application, you can't configure the behavior service-by-service. This second part is likely not in scope for Rice 1.1. If it's decided that's the case then we should create a second jira for a later version which represents improving configurability of store-and-forward.

        Activity

        Hide
        Eric Westfall added a comment -

        The store-and-forward hack was already removed in Rice 2.0. I'm going to resolve this issue as won't fix for now and if we revisit the need for store and forward-style capabilities in the future we can revist and come up with the proper solution.

        Show
        Eric Westfall added a comment - The store-and-forward hack was already removed in Rice 2.0. I'm going to resolve this issue as won't fix for now and if we revisit the need for store and forward-style capabilities in the future we can revist and come up with the proper solution.

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel