July 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBPM-1212) static process variables

by Maciej Swiderski (JIRA)

[ https://jira.jboss.org/browse/JBPM-1212?page=com.atlassian.jira.plugin.sy... ] Maciej Swiderski commented on JBPM-1212: ---------------------------------------- is this something more than variable declaration?! > static process variables > ------------------------ > > Key: JBPM-1212 > URL: https://jira.jboss.org/browse/JBPM-1212 > Project: jBPM > Issue Type: Feature Request > Reporter: Tom Baeyens > Priority: Minor > Fix For: jBPM 4.x > > > Add static variables to process definitions -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2890) Reminder repeat attribute set via expression or variable

by Marta Psenkova (JIRA)

Reminder repeat attribute set via expression or variable -------------------------------------------------------- Key: JBPM-2890 URL: https://jira.jboss.org/browse/JBPM-2890 Project: jBPM Issue Type: Patch Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Marta Psenkova Attachments: reminder_repeat.pvm.r6402.patch In task reminder it is not possible to use variables in repeat attribute, because it is not parsed, e.g.: <task assignee="${user}" g="224,236,193,52" name="myTask"> <reminder duedate="#{myTask_duedate}" template="my-mail-template" repeat="#{myTask_repeat}" /> <transition to="nextStep"/> </task> The solution here is to parse expression when timer (TimerImpl) is created See patch attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPM-2892) support i18n for EL

by Huisheng Xu (JIRA)

support i18n for EL ------------------- Key: JBPM-2892 URL: https://jira.jboss.org/browse/JBPM-2892 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Reporter: Huisheng Xu Fix For: jBPM 4.x Let EL support i18n. Now we could add ResourceBundleELResolver to JbpmELFactoryImpl. then we could use #{resourceBundle['text.title']} to use this resourcebundle message. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-2886) job is not released when the transaction is marked as rollback only

by Adam Laczynski (JIRA)

job is not released when the transaction is marked as rollback only ------------------------------------------------------------------- Key: JBPM-2886 URL: https://jira.jboss.org/browse/JBPM-2886 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Environment: - WebLogic 10.2.3 - jbpm 4.3 - Oracle 10g Reporter: Adam Laczynski Job is not released when the exception occurred during job execution and transaction is marked as rollback only because synchronization cannot be registered in transaction (according to javax.transaction.Transaction#registerSynchronization java doc: @exception RollbackException Thrown to indicate that the transaction has been marked for rollback only). Following exception is thrown: org.jbpm.api.JbpmException: couldn't register synchronization: test1 at org.jbpm.pvm.internal.tx.JtaTransaction.registerSynchronization(JtaTransaction.java:78) at org.jbpm.pvm.internal.cmd.ExecuteJobCmd.handleJobExecutionException(ExecuteJobCmd.java:111) at org.jbpm.pvm.internal.cmd.ExecuteJobCmd.execute(ExecuteJobCmd.java:92) at org.jbpm.pvm.internal.cmd.ExecuteJobCmd.execute(ExecuteJobCmd.java:42) at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42) at org.jbpm.pvm.internal.tx.JtaTransactionInterceptor.executeInNewTx(JtaTransactionInterceptor.java:87) at org.jbpm.pvm.internal.tx.JtaTransactionInterceptor.execute(JtaTransactionInterceptor.java:66) at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55) at org.jbpm.pvm.internal.tx.JtaRetryInterceptor.executeWithRetry(JtaRetryInterceptor.java:52) at org.jbpm.pvm.internal.tx.JtaRetryInterceptor.execute(JtaRetryInterceptor.java:45) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53) at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40) at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43) at org.jbpm.pvm.internal.jobexecutor.JobParcel.run(JobParcel.java:48) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) After that, job could be acquired again but only after the lockMillis (default 30 minutes). IMO in such case the job has to be released because it delay job execution. To achieve it JobExceptionHandler (with small modification) has to be register before invoking job.execute(...) in org.jbpm.pvm.internal.cmd.ExecuteJobCmd:76. Exception could be passed to the handler in the catch block. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Work stopped: (JBPM-1209) support for expressions

by Huisheng Xu (JIRA)

[ https://jira.jboss.org/browse/JBPM-1209?page=com.atlassian.jira.plugin.sy... ] Work on JBPM-1209 stopped by Huisheng Xu. > support for expressions > ----------------------- > > Key: JBPM-1209 > URL: https://jira.jboss.org/browse/JBPM-1209 > Project: jBPM > Issue Type: Feature Request > Components: Runtime Engine > Reporter: Tom Baeyens > Assignee: Huisheng Xu > Fix For: jBPM 4.4 > > Attachments: JBPM-1209-2010-07-01.patch, JBPM-1209.patch > > > this issue incorporates 2 aspects: > * review all attributes in jpdl where expression resolving is appropriate. validate with a test. > * in the java activity, add the capability to refer to the target object with an expression. that way, the java activity can be used to invoke methods on process variables. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1209) support for expressions

by Huisheng Xu (JIRA)

[ https://jira.jboss.org/browse/JBPM-1209?page=com.atlassian.jira.plugin.sy... ] Huisheng Xu resolved JBPM-1209. ------------------------------- Fix Version/s: jBPM 4.4 (was: jBPM 4.x) Resolution: Done > support for expressions > ----------------------- > > Key: JBPM-1209 > URL: https://jira.jboss.org/browse/JBPM-1209 > Project: jBPM > Issue Type: Feature Request > Components: Runtime Engine > Reporter: Tom Baeyens > Assignee: Huisheng Xu > Fix For: jBPM 4.4 > > Attachments: JBPM-1209-2010-07-01.patch, JBPM-1209.patch > > > this issue incorporates 2 aspects: > * review all attributes in jpdl where expression resolving is appropriate. validate with a test. > * in the java activity, add the capability to refer to the target object with an expression. that way, the java activity can be used to invoke methods on process variables. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2648) Candidate-Groups

by Sebastian Castellanos (JIRA)

Candidate-Groups ----------------- Key: JBPM-2648 URL: https://jira.jboss.org/jira/browse/JBPM-2648 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.2 Reporter: Sebastian Castellanos Hi, I have a problem when seeking tasks using candidate-groups. I created tarea1 which has associated candidate-groups "Group1, Group2, Group3. Then I have a user "sebastian" which is a member of Group 1, Group 2 and Group 3. The problem is that when I run taskService().findGroupTasks("sebastian"); I returned a list of 3 tasks equal, Tarea1, Tarea1, Tarea1. When it should be listed just once the task (Tarea1). I'm not sure if it's a conceptual issue or a bug in the API. I would be grateful for your help. P/d: I'm not using swimlane because I had problems with respect to the Fork / Join. Greetings. Sebastian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

6
17
0 / 0

[JBoss JIRA] Created: (JBPM-2533) combine process instances and history process instances in console views

by Tom Baeyens (JIRA)

combine process instances and history process instances in console views ------------------------------------------------------------------------ Key: JBPM-2533 URL: https://jira.jboss.org/jira/browse/JBPM-2533 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Tom Baeyens Assignee: Joram Barrez Fix For: jBPM 4.x in the appropriate console views, runtime process instances need to be combined with history process instances. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2534) add signalling action to console

by Tom Baeyens (JIRA)

add signalling action to console -------------------------------- Key: JBPM-2534 URL: https://jira.jboss.org/jira/browse/JBPM-2534 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Joram Barrez Fix For: jBPM 4.3 signalling capabilities need to be added to the console so that all examples become executable. now there are a couple excluded from deployment. in case of a state activity, offering the signal action is obvious. but we still need to work out in which other situations we offer signalling. if that is not clear, then we could just stick with offering the signal action for all executions for which condition (execution.isActive() && "state".equals(execution.getActivity().getType()) resolves to true -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
9
0 / 0

[JBoss JIRA] Created: (JBPM-2901) add executionId Parameter for TaskQuery

by Michael Wohlfart (JIRA)

add executionId Parameter for TaskQuery --------------------------------------- Key: JBPM-2901 URL: https://jira.jboss.org/browse/JBPM-2901 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.4 Environment: any Reporter: Michael Wohlfart Priority: Trivial Fix For: jBPM 4.4 Please extend the TaskQuery interface and TaskQueryImpl to allow a executionId parameter for creating task queries, there is a patch that implements that in the forum -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2010