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

Take another look at Simple Web Service API for KEW

    Details

    • Similar issues:
      KULRICE-2191Create a "lite" version of WorkflowInfo and WorkflowDocument APIs that can be easily used by non-Java technologies via web services
      KULRICE-4662Clean up KEW services
      KULRICE-4971DataDictionaryIndex currently indexes based on "simple" class name which can result in silent conflicts in DD classes
      KULRICE-9411KEN Web Service URL incorrect in 2.x TRG
      KULRICE-8696Some KEW API classes/services are not accessible via any service locator
      KULRICE-5326Get rid of KualiWorkflowInfo, replace with usage of standard KEW apis
      KULRICE-642Make KEN web auth use the simple web auth login that KEW and KSB use
      KULRICE-2196Create new workflow user service which uses KIM APIs
      KULRICE-2337Create group service plugin for KEW
      KULRICE-12279Make KSBConfigurer handle if web service call fails to remote service registry
    • Rice Module:
      KEW
    • Application Requirement:
      Rice

      Description

      This involves a couple of tasks:

      1) Verify that there is good documentation
      2) Verify that there are not any missing methods or functionality that should be in this API

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          We will also want to gather some requirements/etc. from Kuali Student for this.

          Show
          Eric Westfall added a comment - We will also want to gather some requirements/etc. from Kuali Student for this.
          Hide
          Eric Westfall added a comment -

          Moving to 0.9.4, for following reasons:

          1) Will be moving to KIM API, can replace our UserId hierarchies on WorkflowDocument, WorkflowUtility
          2) Should hopefully be able to use a single API for both java/webservice integration.

          Show
          Eric Westfall added a comment - Moving to 0.9.4, for following reasons: 1) Will be moving to KIM API, can replace our UserId hierarchies on WorkflowDocument, WorkflowUtility 2) Should hopefully be able to use a single API for both java/webservice integration.
          Hide
          Eric Westfall added a comment -

          After retrofitting KEW for KIM, I hope we will be able to export the same service as SOAP as we do for a JavaService rather than needed to maintain a seperate one.

          We may want to look though if it makes sense to add API methods from this API to the primary API.

          Show
          Eric Westfall added a comment - After retrofitting KEW for KIM, I hope we will be able to export the same service as SOAP as we do for a JavaService rather than needed to maintain a seperate one. We may want to look though if it makes sense to add API methods from this API to the primary API.
          Hide
          Eric Westfall added a comment -

          Closing as a duplicate of KULRICE-4555.

          Show
          Eric Westfall added a comment - Closing as a duplicate of KULRICE-4555 .

            People

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

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel