Community
Participate
Working Groups
If the server has a push model, there can (and will) be multiple getTaskData calls on task submission. Besides a performance impact, this can also result in "task has incoming changes" if the push-invoked getTaskData finishes before the SubmitTaskJob getTaskData. Ignoring certain events, while maybe ok for existing tasks, wont work for new tasks. So I think we would need either API for identifying a push-repository and in general don't have the SubmitTaskJob fetch TaskData, or have let the postTaskData method set a state to something like NO_FETCH and the job honor that state.
We could consider adding a flag to suppress fetching of task data. To clarify, are you looking for a way to modify the synchronization behavior of the tasks framework or for an API in SubmitTaskJob, e.g. when directly invoking the job?
synchronization behaviour of the tasks framework. The main issue at hand in my current example is that during submitting a new task (which is a two step process, one creating the server task, one updating it with the taskdata) fires two events from the server, the first one usually coming in before the the submitTaskJob is done. That triggers fetching of taskData too early and causes an incoming notification. Delaying the event processing of "new task" fixes this, but it seems to be a general problem for servers with a push model. So this is not urgent for me, but should get addressed when addressing the support for push model I think.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
