Victoria Vitaver wrote:
Hi,
I have a need to define my ownset of tasks for a custom document type.
Looking at 1.2.x I have a rough picture of how to do it & which classes
to extend(AbstractTask etc).
However, considering the 'better defined' usecase framework developed in
1.4, I am not sure about the longetivity of the 'Task' approach
lifespan(although they do have different aims, I can see how they 'can'
overlap).
Will the 'Workflow/Task' approach be soon depreciated? Or is it here to
stay?
In 1.4 the task concept will still be supported, with some restrictions:
- There have been some changes to the API, so task code will have to be
changed.
- Not all tasks can be scheduled. It is now possible to access the
service manager from a task, this won't be supported when a task is
executed by the scheduler (because the scheduler is a separate servlet).
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
