Details

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

      Description

      implement rule repository
      1. lives in each client app? or in Rice Standalone server?

        Attachments

          Activity

          Hide
          ewestfal Eric Westfall added a comment -

          Assigning this one to myself since I'm doing some work on it in conjunction with Dan.

          Show
          ewestfal Eric Westfall added a comment - Assigning this one to myself since I'm doing some work on it in conjunction with Dan.
          Hide
          ewestfal Eric Westfall added a comment -

          My basic plan here is to work on design and initial implementation of the following:

          1) Integration between KRMS engine ContextProvider and the rule repository.
          2) Design and implement the sequence flow of conversations between the KRMS engine pieces and the rule repository.
          3) Design and implement the actual rule repository remoteable service interface.
          4) Hook up the backend implementation of this service to work that Dan has already done so far. Stub out any additional pieces.
          5) Document the technical design/architecture on a confluence page.

          Show
          ewestfal Eric Westfall added a comment - My basic plan here is to work on design and initial implementation of the following: 1) Integration between KRMS engine ContextProvider and the rule repository. 2) Design and implement the sequence flow of conversations between the KRMS engine pieces and the rule repository. 3) Design and implement the actual rule repository remoteable service interface. 4) Hook up the backend implementation of this service to work that Dan has already done so far. Stub out any additional pieces. 5) Document the technical design/architecture on a confluence page.
          Hide
          ewestfal Eric Westfall added a comment -

          I've been working on the back and forth here between engine and repository. I'm kind of asembling the pieces as I go.

          The relevant entry points are in RuleRepositoryContextProvider, RuleRepositoryService (and the corresponding impl), and RepositoryToEngineTranslator.

          Talked with Peter and Dan, and Dan is planning to work on filling in the implementation behind RuleRepositoryService and connecting it up to the actual database layer.

          Show
          ewestfal Eric Westfall added a comment - I've been working on the back and forth here between engine and repository. I'm kind of asembling the pieces as I go. The relevant entry points are in RuleRepositoryContextProvider, RuleRepositoryService (and the corresponding impl), and RepositoryToEngineTranslator. Talked with Peter and Dan, and Dan is planning to work on filling in the implementation behind RuleRepositoryService and connecting it up to the actual database layer.
          Hide
          ewestfal Eric Westfall added a comment - - edited

          Just wanted to put a quick update on this jira. At this point I've connected the engine up to everything except TermResolvers and simple propositions (which require the term stuff). Tomorrow I'll spend some time familiarizing myself with the term functionality that Peter has built in. Hopefully I will be able to get things hooked up with terms and term resolvers by the end of day thursday and begin working on some unit and integration testing through the end of Friday.

          Note that I've already created ActionTypeService and PropositionTypeService. The former is how custom Action implementstions are plugged into the system and the later is how custom propositions are plugged into the system. There are two "default" implementations of PropositionTypeService, one which is used for compound propositions, the other for "simple" propositions.

          The implementation of the CompoundPropositionTypeService is complete and (should be) functional, but i need to verify with some unit testing.

          The implementation of the SimplePropositionTypeService is where I need to hook Term and TermResolvers in. It's currently stubbed out.

          Show
          ewestfal Eric Westfall added a comment - - edited Just wanted to put a quick update on this jira. At this point I've connected the engine up to everything except TermResolvers and simple propositions (which require the term stuff). Tomorrow I'll spend some time familiarizing myself with the term functionality that Peter has built in. Hopefully I will be able to get things hooked up with terms and term resolvers by the end of day thursday and begin working on some unit and integration testing through the end of Friday. Note that I've already created ActionTypeService and PropositionTypeService. The former is how custom Action implementstions are plugged into the system and the later is how custom propositions are plugged into the system. There are two "default" implementations of PropositionTypeService, one which is used for compound propositions, the other for "simple" propositions. The implementation of the CompoundPropositionTypeService is complete and (should be) functional, but i need to verify with some unit testing. The implementation of the SimplePropositionTypeService is where I need to hook Term and TermResolvers in. It's currently stubbed out.
          Hide
          ewestfal Eric Westfall added a comment -

          Re-assigning to Peter since I'm no longer working on this.

          Show
          ewestfal Eric Westfall added a comment - Re-assigning to Peter since I'm no longer working on this.
          Hide
          gilesp Peter Giles (Inactive) added a comment -

          Changing milestone fix version to m4. This issue corresponds to the "fleshed out Repository" item on the Milestones wiki page.

          Show
          gilesp Peter Giles (Inactive) added a comment - Changing milestone fix version to m4. This issue corresponds to the "fleshed out Repository" item on the Milestones wiki page.
          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:
              gilesp Peter Giles (Inactive)
              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 - 3 weeks
                3w
                Remaining:
                Remaining Estimate - 3 weeks
                3w
                Logged:
                Time Spent - Not Specified
                Not Specified