Skip to main content


Eclipse Community Forums

      Home
Home » Eclipse Projects » Mylyn » Choice between updateTaskFromRepository() or updateTaskFromTaskData()
Choice between updateTaskFromRepository() or updateTaskFromTaskData() [message #43746] Tue, 19 February 2008 14:10 Go to next message
Eclipse UserFriend
I'm working on a generic SQL connector from scratch. The integrators
guide points to the Trac connector.

I can connect to a local or remote test DB and retrieve task data for a
single task.

What I find difficult to understand is the use of the RepositoryTaskData
for any kind of repository. What would be the architectural benefits?
Re: Choice between updateTaskFromRepository() or updateTaskFromTaskData() [message #43875 is a reply to message #43746] Thu, 21 February 2008 23:15 Go to previous message
Eclipse UserFriend
> What I find difficult to understand is the use of the RepositoryTaskData
> for any kind of repository. What would be the architectural benefits?

Elements of the task list are represented by classes that extend
AbstractTask. The task list is always kept in memory and its task model is
limited to the most common attributes to keep it lightweight.

RepositoryTaskData allows connectors to store a custom task model that can
have arbitrary attributes. For Mylyn 2.x it is optional for connector
implementors to support this API. It offers more extensibility and is
required to support rich editing and attachment support but comes with a
higher cost in terms of development effort.

We have are considering to simplify the task data API and making it
mandatory for 3.0 which would make the split between RepositoryTaskData and
AbstractTask less confusing.

Maarten, it would be great if you could file a new bug for this and I'll
post more details about the current ideas to improve the API.

Steffen
Re: Choice between updateTaskFromRepository() or updateTaskFromTaskData() [message #587973 is a reply to message #43746] Thu, 21 February 2008 23:15 Go to previous message
Eclipse UserFriend
> What I find difficult to understand is the use of the RepositoryTaskData
> for any kind of repository. What would be the architectural benefits?

Elements of the task list are represented by classes that extend
AbstractTask. The task list is always kept in memory and its task model is
limited to the most common attributes to keep it lightweight.

RepositoryTaskData allows connectors to store a custom task model that can
have arbitrary attributes. For Mylyn 2.x it is optional for connector
implementors to support this API. It offers more extensibility and is
required to support rich editing and attachment support but comes with a
higher cost in terms of development effort.

We have are considering to simplify the task data API and making it
mandatory for 3.0 which would make the split between RepositoryTaskData and
AbstractTask less confusing.

Maarten, it would be great if you could file a new bug for this and I'll
post more details about the current ideas to improve the API.

Steffen
Previous Topic:Generic Web Connector timeout
Next Topic:Strange behaviour of Mylyn ActivityTimerThread
Goto Forum:
  


Current Time: Thu Nov 20 16:44:30 EST 2025

Powered by FUDForum. Page generated in 0.04065 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly