December 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2558) SpringTransactionInterceptor: Resolve transactionManager by name

by Andries Inze (JIRA)

SpringTransactionInterceptor: Resolve transactionManager by name ---------------------------------------------------------------- Key: JBPM-2558 URL: https://jira.jboss.org/jira/browse/JBPM-2558 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0, jBPM 4.1 Reporter: Andries Inze Priority: Optional SpringTransactionInterceptor searches for any PlatformTransactionManager in the environment. An alternative way of specifying the name would be appropriate. e.g. <spring-transaction-interceptor name="myTransactionInterceptor" /> Fix should only be limited to adding a property to the binding and using the propery in https://anonsvn.jboss.org/repos/jbpm/jbpm4/trunk/modules/pvm/src/main/jav... -- 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

14 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2657) No override of convenience methods in SpringConfiguration

by Walter Seymore (JIRA)

No override of convenience methods in SpringConfiguration --------------------------------------------------------- Key: JBPM-2657 URL: https://jira.jboss.org/jira/browse/JBPM-2657 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.2 Environment: Spring Reporter: Walter Seymore Priority: Minor Fix For: jBPM 4.3 Attachments: ProcessEngineImpl.patch When using spring to define some components, (specifically the ones exposed in the convenience methods provided by ProcessEngine e.g. getTaskService(), getExecutionService() etc.), trying to retrieve these from the process engine does not go through the overridden get(Class c) method. Either the SpringConfiguration should also override these methods, or even better, the ProcessEngineImpl should use the get(Class c) method for resolving them instead of going straight to the wire context. -- 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

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2646) jBPM 4.2 integration with Spring 2.5.6 fails

by Alexandru Ionita (JIRA)

jBPM 4.2 integration with Spring 2.5.6 fails -------------------------------------------- Key: JBPM-2646 URL: https://jira.jboss.org/jira/browse/JBPM-2646 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.2 Environment: jbpm 4.2 Reporter: Alexandru Ionita -- 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

14 years, 6 months

2
4
0 / 0

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

by Sebastian Schneider (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1209?page=com.atlassian.jira.plug... ] Sebastian Schneider commented on JBPM-1209: ------------------------------------------- Might be related: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=164874 > support for expressions > ----------------------- > > Key: JBPM-1209 > URL: https://jira.jboss.org/jira/browse/JBPM-1209 > Project: jBPM > Issue Type: Feature Request > Reporter: Tom Baeyens > Assignee: Joram Barrez > Fix For: jBPM 4.3 > > > 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-2632) move XPathScriptEngine classes from bpmn to pvm

by Tom Baeyens (JIRA)

move XPathScriptEngine classes from bpmn to pvm ----------------------------------------------- Key: JBPM-2632 URL: https://jira.jboss.org/jira/browse/JBPM-2632 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Joram Barrez Fix For: jBPM 4.3 from /jbpm-bpmn/src/main/java/com/sun/script/xpath to /jbpm-pvm/src/main/java/org/jbpm/pvm/internal/script -- 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

14 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2678) Can't deploy jBPM process from JBDS 2.1

by Alejandro Guizar (JIRA)

Can't deploy jBPM process from JBDS 2.1 --------------------------------------- Key: JBPM-2678 URL: https://jira.jboss.org/jira/browse/JBPM-2678 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.8 Reporter: Alejandro Guizar Assignee: Alejandro Guizar Fix For: jBPM 3.2.9 Project issue for SOA-1586. -- 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

14 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2492) GetOutcomes returns an additional Outcome than what is already specified than the

by Shekhar Vemuri (JIRA)

GetOutcomes returns an additional Outcome than what is already specified than the ---------------------------------------------------------------------------------- Key: JBPM-2492 URL: https://jira.jboss.org/jira/browse/JBPM-2492 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.CR1 Reporter: Shekhar Vemuri Fix For: jBPM 4.1 Description is below: It was decided in a discussion in the forum(referenced in this issue) that we would not add the additional transition to the list of transitions that are available as part of completing a task. Problem: Is there a particular reason for why GetOutComes does this? Code: Set<String> outcomes = new HashSet<String>(); outcomes.add(Task.STATE_COMPLETED); .. logic to add other transitions specified in the activity. When the TaskService.getOutComes(long taskDbId) is called with a task id it returns completed as an entry in the list of Transitions that will eventually be shown to the user. But this particular transition is not even being modeled in the process_definition. There are other places in the code, where in if a transition/outcome name is not specified then the transition is assumed to the 'completed' and special handling is done, Code: if (Task.STATE_COMPLETED.equals(signalName)) { if (outgoingTransitions.size()==1) { transition = outgoingTransitions.get(0); } else { transition = activity.getDefaultOutgoingTransition(); } } The above snippet is from TaskActivity. What is the reasoning behind adding this to the transitions that can be taken out of a Task node? _________________ -- 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

14 years, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBPM-2006) drools integration

by Tom Baeyens (JIRA)

drools integration ------------------ Key: JBPM-2006 URL: https://jira.jboss.org/jira/browse/JBPM-2006 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Priority: Minor Fix For: jBPM 4.0.0.Beta2 * exclusive condition evaluation * configurable process variables to submit as facts * make process variables available as rules global variables * investigate logging integration * investigate joint deployment of rules in process archive -- 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

14 years, 7 months

5
18
0 / 0

[JBoss JIRA] Created: (JBPM-2538) Make a TaskQuery resuable

by Joram Barrez (JIRA)

Make a TaskQuery resuable ------------------------- Key: JBPM-2538 URL: https://jira.jboss.org/jira/browse/JBPM-2538 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Reporter: Joram Barrez Priority: Minor Fix For: jBPM 4.3 Queries can't be reused: TaskQuery openTasksQuery = taskService.createTaskQuery().state(Task.STATE_OPEN); List<Task> openTasks = openTasksQuery.list(); openTasks = openTasksQuery.list(); The first time list() is called, the HQL query that is produced is fine: select task from org.jbpm.pvm.internal.task.TaskImpl as task where task.state = 'open' The second time however, the query is wrong: select task from org.jbpm.pvm.internal.task.TaskImpl as task and task.state = 'open' This due to the fact that in AbstractQuery, a boolean is remembered for the where clause: rotected void appendWhereClause(String whereClause, StringBuilder hql) { if (isWhereAdded) { hql.append(" and "); } else { isWhereAdded = true; hql.append("where "); } hql.append(whereClause); } In the second call, the 'isWhereAdded' boolean is set to true (due to the first call), which leads to not using the where clause and resulting in a wrong query. -- 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

14 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-2508) report initialization crashes the console

by Tom Baeyens (JIRA)

report initialization crashes the console ----------------------------------------- Key: JBPM-2508 URL: https://jira.jboss.org/jira/browse/JBPM-2508 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Tom Baeyens Assignee: Heiko Braun Fix For: jBPM 4.2 First time when the reports are accessed, the request times out and the console cannot show the reports. Reports cannot be made visible afterwards. Workaround: log out and log back in. -- 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

14 years, 7 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues December 2009