January 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1358) Add QA for derby

by Thomas Diesler (JIRA)

Add QA for derby ---------------- Key: JBPM-1358 URL: http://jira.jboss.com/jira/browse/JBPM-1358 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1359) Add QA for firebird

by Thomas Diesler (JIRA)

Add QA for firebird ------------------- Key: JBPM-1359 URL: http://jira.jboss.com/jira/browse/JBPM-1359 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1361) Add QA for informix

by Thomas Diesler (JIRA)

Add QA for informix ------------------- Key: JBPM-1361 URL: http://jira.jboss.com/jira/browse/JBPM-1361 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBPM-1016) ProcessState 'leave' method always returns default transition

by Ronald van Kuijk (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1016?page=com.atlassian.jira.plug... ] Ronald van Kuijk commented on JBPM-1016: ---------------------------------------- Is there a new issue made than to track this? Just closing and mentioning it will be in 4.0 is plain wrong. > ProcessState 'leave' method always returns default transition > -------------------------------------------------------------- > > Key: JBPM-1016 > URL: https://jira.jboss.org/jira/browse/JBPM-1016 > Project: JBoss jBPM > Issue Type: Patch > Components: Core Engine > Affects Versions: jBPM 3.2.0 > Reporter: Randy Gullett > Assignee: Alejandro Guizar > > The leave method for ProcessStates currently automatically takes the default transition despite taking a transition as a parameter. Can it be modified so that it leaves by the transition passed in (if it isn't null) like you'd expect it to? I want to be able to short-circuit my subprocesses in certain scenarios. See the method as it's currently coded below. > public void leave(ExecutionContext executionContext, Transition transition) { > ProcessInstance subProcessInstance = executionContext.getSubProcessInstance(); > Token superProcessToken = subProcessInstance.getSuperProcessToken(); > // feed the readable variableInstances > if ((variableAccesses != null) && (!variableAccesses.isEmpty())) { > ContextInstance superContextInstance = executionContext.getContextInstance(); > ContextInstance subContextInstance = subProcessInstance.getContextInstance(); > // loop over all the variable accesses > Iterator iter = variableAccesses.iterator(); > while (iter.hasNext()) { > VariableAccess variableAccess = (VariableAccess) iter.next(); > // if this variable access is writable > if (variableAccess.isWritable()) { > // the variable is copied from the sub process mapped name > // to the super process variable name > String mappedName = variableAccess.getMappedName(); > Object value = subContextInstance.getVariable(mappedName); > String variableName = variableAccess.getVariableName(); > log.debug("copying sub process var '"+mappedName+"' to super process var '"+variableName+"': "+value); > if (value!=null) { > superContextInstance.setVariable(variableName, value, superProcessToken); > } > } > } > } > // fire the subprocess ended event > fireEvent(Event.EVENTTYPE_SUBPROCESS_END, executionContext); > // remove the subprocess reference > superProcessToken.setSubProcessInstance(null); > > // We replaced the normal log generation of super.leave() by creating the log here > // and overriding the addNodeLog method with an empty version > superProcessToken.addLog(new ProcessStateLog(this, superProcessToken.getNodeEnter(), new Date(), subProcessInstance)); > // call the subProcessEndAction > [b]super.leave(executionContext, getDefaultLeavingTransition());[/b] } > The bold line could be replaced by something like: > if(transition != null) { > super.leave(executionContext, transition); > } else { > super.leave(executionContext, getDefaultLeavingTransition()); -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1375) Provide a way to determine the node type

by Mauro Molinari (JIRA)

Provide a way to determine the node type ---------------------------------------- Key: JBPM-1375 URL: http://jira.jboss.com/jira/browse/JBPM-1375 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: API Affects Versions: jPDL 3.2.3 Reporter: Mauro Molinari If you need to iterate over the nodes of a ProcessDefinition: final List processNodes = processDefinition.getNodes (); for (int x = 0; x < processNodes.size (); x++) { final org.jbpm.graph.def.Node node = (org.jbpm.graph.def.Node) processNodes.get (x); // ... } and you need to determine the actual type of a node, you cannot use instanceof because of the potential use of CGLIB proxies. So, there's no *clean* way to determine the actual type of a node!! Using the HibernateProxy workaround cited in the JBoss Forum reference attached, is not acceptable IMHO, because you're loosing the transparency against the underlying persistence technology. Moreover, it doesn't seem to work in the tests we're doing. Using the alternative toString() workaround is also a dirty trick, because the toString() implementation might change and toString() shouldn't be used for this kind of things. In another discussion: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156233 another user is experiencing our exact problem with the StartState: but we're not guaranteed that the same issue doesn't happen with other node types. I can hardly accept the fact that a XXNode instance can't be cast to an XXNode object reference, however if this is the case, I think a clean way to determine the type of a node should then be provided by the jBPM API. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
7
0 / 0

[JBoss JIRA] Commented: (JBPM-1450) Disable jBPM logging

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1450?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBPM-1450: -------------------------------------- I had a conversation with Trevor, we believe that this should be fixed as part of the maven SOA profile that exists already. To make progress I would schedule this to 3.3.2 so you can have a look at it over the next 4 weeks. > Disable jBPM logging > -------------------- > > Key: JBPM-1450 > URL: https://jira.jboss.org/jira/browse/JBPM-1450 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Console > Reporter: Mark Little > Assignee: Alejandro Guizar > Fix For: jBPM 3.3.2 GA , SOA 4.2 CP03, SOA 4.3 > > -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1450) Disable jBPM logging

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1450?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1450: --------------------------------- Fix Version/s: jBPM 3.3.2 GA > Disable jBPM logging > -------------------- > > Key: JBPM-1450 > URL: https://jira.jboss.org/jira/browse/JBPM-1450 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Console > Reporter: Mark Little > Assignee: Alejandro Guizar > Fix For: jBPM 3.3.2 GA , SOA 4.2 CP03, SOA 4.3 > > -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1864) expose task variables through the task service api

by Tom Baeyens (JIRA)

expose task variables through the task service api -------------------------------------------------- Key: JBPM-1864 URL: https://jira.jboss.org/jira/browse/JBPM-1864 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Task Reporter: Tom Baeyens Assignee: Alejandro Guizar Fix For: jBPM 4.0.0 Alpha1 we have to discuss first how we'll deal with task and 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

17 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1862) expose candidates and roles through the task service api

by Tom Baeyens (JIRA)

expose candidates and roles through the task service api -------------------------------------------------------- Key: JBPM-1862 URL: https://jira.jboss.org/jira/browse/JBPM-1862 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Alejandro Guizar Fix For: jBPM 4.0.0 Alpha1 -- 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

17 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-1863) expose task comments throught the taskservice api

by Tom Baeyens (JIRA)

expose task comments throught the taskservice api ------------------------------------------------- Key: JBPM-1863 URL: https://jira.jboss.org/jira/browse/JBPM-1863 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Task Reporter: Tom Baeyens Assignee: Alejandro Guizar Fix For: jBPM 4.0.0 Alpha1 -- 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

17 years, 3 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2009