Details

    • Type: Task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.0-m9, 2.0
    • Component/s: Version Compatibility
    • Labels:
      None
    • Rice Module:
      KEW
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Implement support for replacing "object remoting" concept
      1. modify document type xml (and others) so it can support service name instead of post processor.
      2. clients will need to start publishing their services... this would need to be documented.
      3. Also, these different service interfaces don't currently use DTOs, so DTOs will need to be implemented and used
      4. These service interfaces will also need to be annotated.
      5. Document search generator, result set processor, searchable attribute will be a big part of this

        Attachments

          Issue Links

            Activity

            Hide
            ewestfal Eric Westfall added a comment -

            I think at least some of this work is covered by some other jiras i've created, so reducing the estimate on this from 3 weeks to 2 weeks.

            Show
            ewestfal Eric Westfall added a comment - I think at least some of this work is covered by some other jiras i've created, so reducing the estimate on this from 3 weeks to 2 weeks.
            Hide
            ewestfal Eric Westfall added a comment -

            Going to continue separating out specific services into specific jiars. Main work that needs to be done here is to deal with framework to allow for easy publishing of these service by clients. Also includes modification of the RuleAttribute implementation so that service names instead of classnames can be set up inside of the KREW_RULE_ATTR_T table.

            Show
            ewestfal Eric Westfall added a comment - Going to continue separating out specific services into specific jiars. Main work that needs to be done here is to deal with framework to allow for easy publishing of these service by clients. Also includes modification of the RuleAttribute implementation so that service names instead of classnames can be set up inside of the KREW_RULE_ATTR_T table.
            Hide
            ewestfal Eric Westfall added a comment -

            Here is the list of services that were using object remoting in rice 1.0.x, need to make sure we have jiras for all of these:

            https://spreadsheets.google.com/a/kuali.org/spreadsheet/ccc?key=0AtGm_DS4ERBfdFFtNmVBbkJFTnpxX2E0cTJndkZuLXc&hl=en_US#gid=0

            Show
            ewestfal Eric Westfall added a comment - Here is the list of services that were using object remoting in rice 1.0.x, need to make sure we have jiras for all of these: https://spreadsheets.google.com/a/kuali.org/spreadsheet/ccc?key=0AtGm_DS4ERBfdFFtNmVBbkJFTnpxX2E0cTJndkZuLXc&hl=en_US#gid=0
            Hide
            ewestfal Eric Westfall added a comment - - edited

            The only components that are actually required be remotable as soap services are:

            1. WorkflowAttribute
            2. SecurityAttribute
            3. SearchableAttribute
            4. RuleValidationAttribute
            5. DocumentSearchGenerator
            6. DocumentSearchResultProcessor
            7. DocumentSearchCriteriaProcessor
            8. CustomActionListAttribute


            For the remaining ones on the googledoc, it might ultimately be worthwhile for some of them to be remotable (like post processor) but it really wasn't supported in Rice 1.0.x so we shouldn't need to provide remoting support for these as part of Rice 2.0.

            Show
            ewestfal Eric Westfall added a comment - - edited The only components that are actually required be remotable as soap services are: WorkflowAttribute SecurityAttribute SearchableAttribute RuleValidationAttribute DocumentSearchGenerator DocumentSearchResultProcessor DocumentSearchCriteriaProcessor CustomActionListAttribute For the remaining ones on the googledoc, it might ultimately be worthwhile for some of them to be remotable (like post processor) but it really wasn't supported in Rice 1.0.x so we shouldn't need to provide remoting support for these as part of Rice 2.0.
            Hide
            ewestfal Eric Westfall added a comment -

            Support for object remoting was removed a long time ago, most of the services that were originally using it have since been migrated over to the standard service model or are in progress (with their own jiras tracking that work). So I'm resolving this issue.

            Show
            ewestfal Eric Westfall added a comment - Support for object remoting was removed a long time ago, most of the services that were originally using it have since been migrated over to the standard service model or are in progress (with their own jiras tracking that work). So I'm resolving this issue.
            Hide
            jcoltrin Jessica Coltrin (Inactive) added a comment -

            Closing since these items are now in the release notes.

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

              People

              • Assignee:
                Unassigned
                Reporter:
                masargen Matt Sargent
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 week
                  1w
                  Remaining:
                  Remaining Estimate - 1 week
                  1w
                  Logged:
                  Time Spent - Not Specified
                  Not Specified