Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Finish work on Rice IMPL
    1. KCB and KEN stuff should be easy to work with by moved into a KEN IMPL Module
    2. KNS package should be move up to KNS module
    3. Module service base should be move up from KRAD to the KRAD APP or Framework
      1. allows for core service and location out of rice impl
    4. Analyze KEW to see how it needs to be refactored to it's own module
    5. Analyze KIM as well
    6. Analyze the KRAD pieces and decide which needs to go where by package and classes
  2. Run latex tool against our code
  3. Get rid of groovy stuff
  4. Look at Web Content modularity remaining work
    1. Focus on KRAD and what makes most sense for it being our Web Content delivery method going forward
  5. Figure out how to fix the EBO frameworkissue and replace it

Rice impl work Discussion Notes KCW2012


  • Run latex tool against our code
  • Get rid of groovy stuff
  • Another idea would be to push this out to the 3.0 release, KRAD and JPA and such
  • Need to do an analysis of the current module from the KRAD/KNS viewpoint and then another group look at the non-KRAD/KNS pieces
    • Do we still need and API and an IMPL for krad modules?
      • In anything that we expect the public to extend, we should have an API.  
      • We need to look at what we can do to making extendable items safe and well documented
      • Would be nice to forgo the IMPL side if we can, but it may not always be the case
    • Want to see KRAD be well packaged and modularized
  • Need to know if we can overlay multiple war packages in one jar file
  • KFS uses EBOs extensively so we need to ensure we don't mess things up while/when we do this with our new design
    • If this is an instance of an externalized business object...