To Do
Oddjob-0.29.0 (Due January 2010)
Not sure yet, but choices are:
- A lot more documentation.
- Logging - Remove the logger property
from jobs as it is never used. Look at recovering log
messages from the log file, or some other store, on startup.
- Re-think persistence of Oddjob jobs. Hard reset should remove
all persisted state for that Oddjob job and it's children including
nested Oddjobs. The situation at the moment is a bit confusing.
- Improve database persistence. Use BLOBs instead of the Object
data type and so support the majority of Databases.
- Use the idea of flavours introduced for services for the
supports tags in the designer. At the moment a date can be assigned
to an xml field becuase they are both strings. There should be
string flavours 'xml' and 'date'.
- Properties - Make working with properties more intuitive. Maybe display
the actual properties set in the properties job in the monitor instead
of the job's properties.
- Reference Doc - Replace the existing JavaDoc tag based reference
with something more dynamic. Annotations maybe.
- Web Front End - Replace the clunky Struts front end with
something AJAXy.
|