Search this site

Contact us

Do you have problems with site or you want to give us a feedback? Use our mailing list.

Milestone 0.1 Released 5-Aug-2009

  • RobotHandlers configurable using annotations to handle wave events
  • Provide basic, annotation based event to handler method mapping
  • [Issue 1] Automaticly generated capabilities.xml based from registered handlers
  • Automaticly generated profile based on robot configuration

Milestone 0.2 Released 24-Aug-2009

  • [Issue 2] Get rid of Velocity which is used just for capabilities document generation
  • Enhance architecture - decompose and consolidate, define interfaces
    • [Issue 3] extract RobotHandlerAdapter - adapter which will be able to invoke Robot Handler's method with any combination of bundle, event, wavelet arguments
    • [Issue 4] extract capabilities handling to separate controller
    • [Issue 5] extract profile handling to separate controller
    • Extract serialiser
    • [Issue 7] Extract Robot from RobotController
      • RobotController will be responsible for HTTP handling, parsing, robot invocation
      • Robot will be responsible for event handling
      • Robot's interface will be springless and servletless
  • [Issue 6] Consolidate logging and error handling
  • [Issue 8] Provide extensible filtering mechanism over the handler method calls - configurable chain of filters will decide wheather the method will or will not be called for certain event (eg. based on users permissions or presence of some word in the document).

Milestone 0.3 Released 15-Oct-2009

  • [Issue 9] Update version of google-wave-api.jar to version 20090813
  • Release parroty-robot example and related tutorial
  • Release spring-wave-calendar example and related tutorial
  • [Issue 12] Implement filter for FORM_BUTTON_CLICKED event enabling to specify conrete button name
  • [Issue 10] Update version of google-wave-api.jar to version 20090916
  • [Issue 11] Implement capabilities.xml generation to be compatible with it's new format using 'context' attribute instead of 'content' used before
  • [Issue 13] Provide possibility to fill handling context by filters - can be than used by form binding, ...

Milestone 0.4

  • [Issue 14] Introduce contexts for Event, Bundle and Wavelet

Milestone 1.0

  • Form binding
  • Workflow support
  • Enable to have robot name and robot avatar generated dynamicaly so they can reflect robot's state
  • Robot usage statistics


Comments