Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Mylyn » Choice between updateTaskFromRepository() or updateTaskFromTaskData()
Choice between updateTaskFromRepository() or updateTaskFromTaskData() [message #43746] Tue, 19 February 2008 19:10 Go to next message
maarten meijer is currently offline maarten meijerFriend
Messages: 146
Registered: July 2009
Senior Member
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?

Report message to a moderator

Re: Choice between updateTaskFromRepository() or updateTaskFromTaskData() [message #43875 is a reply to message #43746] Fri, 22 February 2008 04:15 Go to previous message
Steffen Pingel is currently offline Steffen PingelFriend
Messages: 706
Registered: July 2009
Senior Member
> 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

Report message to a moderator

Re: Choice between updateTaskFromRepository() or updateTaskFromTaskData() [message #587973 is a reply to message #43746] Fri, 22 February 2008 04:15 Go to previous message
Steffen Pingel is currently offline Steffen PingelFriend
Messages: 706
Registered: July 2009
Senior Member
> 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

Report message to a moderator

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

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Thu Apr 25 04:19:57 GMT 2024

Powered by FUDForum. Page generated in 0.03531 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