Details

    • Type: Sub Task Sub Task
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-m3, 2.0
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Similar issues:
      KULRICE-4623Research the best strategy for keeping postal-related data up to date
      KULRICE-10217Determine how best to fix BusinessObjectRefreshTest.testEagerRefreshEboField for County data object
      KULRICE-4366cannot connect to remote kfs services
      KULRICE-5196Determine if Pessimistic locks need to move to the server as server-side remoted services
      KULRICE-3348KIM RoleService and DAOs Must not reference the Service Layer
      KULRICE-6694Determine if KRMS Type Services can be properly exported to the service bus and used remotely
      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-6509Synchronize with remote services on KSB startup
      KULRICE-3890Determine how best to handle persistence, attached/detached, and lazy loading for the BusinessObjectService in the context of KNS
      KULRICE-4666Evaluate "remote" KIM services
    • Application Requirement:
      Rice
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Runtime exceptions generated from JAX-WS are returned as a general SoapFaultException when invoked by a java client. In order for the exception to be defined in a WSDL as a fault and be binded against by both a client and server, the exception must be annotated with @WebFault. We, however, can't modify Java standard API runtime exceptions (such as InvalidStateException and IllegalArgumentException). This results in an inconsistent API for services classes that can operate in both local mode and remote model

      We need to evaluate whether we should subclass these classes and annotate with @WebFault, try to shoehorn those exception classes into a common exception type using an XmlAdapter, or simply change API documentation to only say that it throws RuntimeExceptions under certain conditions.

        Activity

        Hide
        Jason Whaley (Inactive) added a comment -

        Completed as part of commit in https://test.kuali.org/svn/rice/trunk@16599

        Show
        Jason Whaley (Inactive) added a comment - Completed as part of commit in https://test.kuali.org/svn/rice/trunk@16599
        Hide
        Jessica Coltrin (Inactive) added a comment -

        Closing since these items are now in the release notes.

        Show
        Jessica Coltrin (Inactive) added a comment - Closing since these items are now in the release notes.

          People

          • Assignee:
            Jason Whaley (Inactive)
            Reporter:
            Jason Whaley (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel