Re: [mylyn-integrators] Startup help for writing new connector

[Steffen Pingel <steffenp@xxxxxx>]

> > To date, connectors have been handling conflicts of this nature in the
> > query page ui. As you point out, this is not ideal and we are
> > improving this for Mylyn 3.0. The framework will guard against handle
> > conflicts of this nature and throw the appropriate exceptions where
> > necessary. To follow resolution of this issue, consider adding
> > yourself to the cc:
> >
> >    234767: make sure handles are unique within task list
> >    https://bugs.eclipse.org/bugs/show_bug.cgi?id=234767
>
> Maybe check out that bug and confirm that it's fixed.  I haven't used
> 3.0, yet, so I'm not sure how this works from the connector author's
> perspective.

Previously the handle (unique identifier) of a query was equal to its name and 
therefore the name had to be unique within the task list. This limitation has 
been lifted in Mylyn 3.0 and it is now legal to create queries that have the 
same name. The UI will prevent this (in most cases) though to avoid 
confusion.

> > After closing and reopening the test workbench, the synchronizing is
> > gone. The query was obviously saved wrong and/or non-persistent.
>
> In 2.3, I think that you needed the
> org.eclipse.mylyn.tasks.ui.repositories extension point, where you would
> identify your externalizer with the taskListFactory.  That extension
> identified a AbstractTaskListFactory subclass, and it was used by Mylyn
> in persisting queries and tasks in the Task List.  I believe that these
> APIs relied on the ability to convert a query to and from a URL.
>
> I suspect that some of this API has changed for Mylyn 3.0.

One of the major differences in Mylyn 3.0 is that the life-cycle of task and 
query objects is now entirely managed in the tasks framework. That means 
there is no need for connector implementors to provide custom classes for 
queries and tasks or to handle persistance. Once a task or query is added to 
the task list the it will be saved and restored by the framework.

Steffen

-- 
Steffen Pingel - steffenp@xxxxxx - http://steffenpingel.de