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

The standalone version of WorkflowDocumentActionsService should always be called when kew.mode is Thin or Remote

    Details

    • Type: Bug Fix Bug Fix
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.1
    • Fix Version/s: 2.1.1
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-7609In thin and remote mode, interaction with WorkflowDocumentActionsService is ocurring against endpoints published be applications other than the standalone server
      KULRICE-4498Object remoting for SecurityAttributes is not being used correctly
      KULRICE-3323remote service invocations failing in load balanced scenario
      KULRICE-4528Implement ability for rice server to know what version of a client server they are calling
      KULRICE-12279Make KSBConfigurer handle if web service call fails to remote service registry
      KULRICE-4622When running with standalone Rice, ImmediateEmailService never runs locally
      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-9616Standalone env
      KULRICE-6749Configure rice sample app as a client app running against a standalone server
      KULRICE-4110Externalizable BO lookups and inquiries don't work with standalone Rice
    • Rice Module:
      KEW
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      At IU, we have a client application running in THIN mode for KEW and they kept having issues with hitting the correct workflowDocumentActionsService.

      error -

      HTTP response '404: Not Found' when communicating with http://localhost:8080/sissadmn-dev/rice2/remoting/soap/kew/v2_0/workflowDocumentActionsService
      

      SIS has the same service name, so we need to fetch that service by application id (RICE) for remote clients

      for the standalone server, "RICE" is the application id but for the sample app it's TRAVEL So probably need to have some kind of configuration parameter that indicates the application id to use for interacting with KEW and default it to RICE.

        Issue Links

          Activity

          Hide
          Shannon Hess added a comment -

          I named the configuration parameter standalone.application.id, but can change it if there is a better name.

          <!-- This is used to get the standalone version of WorkflowDocumentActionsService when kew.mode is REMOTE or THIN -->
          <param name="standalone.application.id" override="false">RICE</param>

          Show
          Shannon Hess added a comment - I named the configuration parameter standalone.application.id, but can change it if there is a better name. <!-- This is used to get the standalone version of WorkflowDocumentActionsService when kew.mode is REMOTE or THIN --> <param name="standalone.application.id" override="false">RICE</param>

            People

            • Assignee:
              Shannon Hess
              Reporter:
              Shannon Hess
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel