search

calebpowell / jbpm-instance-migrator

Automatically exported from code.google.com/p/jbpm-instance-migrator
1 stars 0 forks source link

Migrate Task Nodes #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
When migrating a process instance, the related task nodes will not be migrated.

Version: 0.1
       (jbpm-instance-migration-0.1-SNAPSHOT)

Original issue reported on code.google.com by afrasiab...@gmail.com on 23 Dec 2009 at 4:05

GoogleCodeExporter commented 9 years ago 
How soon do you need to see this feature? Would something before the new year be
adequate?

Original comment by caleb.po...@gmail.com on 23 Dec 2009 at 8:13

GoogleCodeExporter commented 9 years ago

Original comment by caleb.po...@gmail.com on 23 Dec 2009 at 8:21

GoogleCodeExporter commented 9 years ago 
Before the new year is perfect! I appreciate you anyway.

Original comment by afrasiab...@gmail.com on 25 Dec 2009 at 10:46

GoogleCodeExporter commented 9 years ago 
Could you provide me with a test case or an example of what you would expect to 
occur
when a token is mapped from a TaskNode in an old ProcessInstance to a new
ProcessInstance? As far as I can tell, TaskNode's should be mapped. I have 
wrote a
unit test to confirm this
(http://code.google.com/p/jbpm-instance-migrator/source/browse/trunk/jbpm-instan
ce-migrator/src/test/java/org/jbpm/instance/migration/TaskNodeMigratorTest.java)
.

Were you running into a specific problem?

Original comment by caleb.po...@gmail.com on 1 Jan 2010 at 5:22

GoogleCodeExporter commented 9 years ago 
By "Task" I mean "org.jbpm.taskmgmt.exe.TaskInstance" (as well as an anonymous 
said
in your blog 
http://calebpowell.blogspot.com/2009/06/jbpm-migrations-our-approach.html :

    "...I did not see how the current code handles existing taskintances. ... August 26,
2009 12:18 PM ")

Following code snippet may complete my requirements:

    Collection<TaskInstance> taskInstances =
processInstance.getTaskMgmtInstance().getTaskInstances();

By the way, we may consider another issue in the "JBPM Migrator". When the 
migration
completed, we may end the old process instance and cancel all its task 
instances.
Otherwise the old process is alive yet and can continue to survive. For example 
we
have a task list in our system in which every user can view his/her works. 
Every work
is indeed a TaskInstance. So, if we don't cancel the task instances of the old
process, the user view two copies of a single task in his/her task list. 
Moreover,
the process itself is alive yet and may be ended. Following method may be used 
to
stop the old process (I found some parts in a website):

/**
 * Terminates the given process instance and cancel all related open task instances.
 * 
 * @param processInstance Process Instance to be stopped. 
 */
public void stopProcessInstance(Session session, JbpmContext jbpmContext, Long
processId) {
    ProcessInstance processInstance = loadProcessInstance(session, processId);
    @SuppressWarnings("unchecked")
    Collection<TaskInstance> taskInstances = processInstance
            .getTaskMgmtInstance().getTaskInstances();

    // Cancel all task instances of the process instance.
    for (TaskInstance task : taskInstances) {
        if (!task.hasEnded()) {
            task.setSignalling(false);
            task.cancel();
            jbpmContext.save(task);
        }
    }

    // End the process instance itself.
    processInstance.end();
    jbpmContext.save(processInstance);
}

Best regards,
Afrasiabi

Original comment by afrasiab...@gmail.com on 6 Jan 2010 at 12:06

GoogleCodeExporter commented 9 years ago 
Thanks Afrasiabi,

I think I understand your requirement. I will start working on this.

Original comment by caleb.po...@gmail.com on 7 Jan 2010 at 2:55

GoogleCodeExporter commented 9 years ago 
Hi Caleb,
Do you have any estimation about when completing this feature?

(Can I know your email? My email is afrasiabian@gmail.com)
Thanks.

Original comment by afrasiab...@gmail.com on 13 Jan 2010 at 2:28

GoogleCodeExporter commented 9 years ago 
Hi Afrasiabian,

I sent you an mail. Did you get it?  You can get in touch with me at
caleb.powell<at>gmail<dot>com

Original comment by caleb.po...@gmail.com on 19 Jan 2010 at 9:57

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Hi ,

Your tool is becoming something of immense help to our project team.
However we are facing the exact same issue as reported by Afrasiabian above.
In our application also we have a list of taskinstances and every user can view 
his/her works. Each work/inbox is actually a taskinstance.

I understand that the migration of taskinstances is not part of the 
implementation of this tool yet however we are planning to develop it as we 
need to complete our migration much sooner (in about 1-2 months).

Can you please send me any already implemented code that you might have written 
for this issue so that we can have a look at it and continue on it or 
understand how we can implement it effectively.

My email is is sudaksh_chohan<at>yahoo<dot>com 
official email id is sudaksh.chohan<at>tavant<dot>com

I am willing to participate in the open source development of this tool also.

Thanks,
Sudaksh Chohan

Original comment by sudaksh....@gmail.com on 5 Oct 2010 at 10:55

GoogleCodeExporter commented 9 years ago 
What is the status of this issue? I need a way to replicate a TaskInstance into 
the new  processInstance created. Thanks

Original comment by voloth...@gmail.com on 12 Dec 2011 at 3:34