Bug 217953

Description Steffen Pingel 2008-02-05 21:23:00 EST

See discussion on bug 209327 (comment 13 and following).

The review of the task list serialization code indicated that the task list serialization and import/export code probably needs a larger refactoring. The current logic is spread over multiple classes and duplicates quite a bit of code. Mylyn should provide a facility to import and exports through a single interface. 

These entities need to be serialized:

 * Task
 * Task Data (for rich editing / offline support)
 * Task Context
 * Task Repository

This could be implemented in a new class that serves as a facade to TaskListWriter, TaskRepositoriesExternalizer, TaskDataManger and InteractionContextManager. The class could be made public API and would support import and export of these entities through a single stream. The interface could look similar to this:

class TaskExternalizer {

 void write(AbstractTaskContainer[] items, OutputStream out, IProgressMonitor monitor);
 
 Result read(InputStream in, IProgressMonitor monitor);

}

class Result {

 IStatus getStatus();

 void commit(TaskList taskList);
  
}

The Result class would provide facilities for user interaction in case of problems (e.g. when a task is imported that already exists).