March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-905) Latest jpdl build.xml has broken dependency

by Bill Middleton (JIRA)

Latest jpdl build.xml has broken dependency -------------------------------------------- Key: JBPM-905 URL: http://jira.jboss.com/jira/browse/JBPM-905 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 alpha 1 Environment: Windows build using Ant 1.6 Reporter: Bill Middleton Assigned To: Tom Baeyens The latest updates to the jpdl build.xml (jbpm.3/jpdl/dist/build.xml v1.22) introduce a small bug. The target test.suite.distribution depends on "clean, dist", but there doesn't seem to be any dist target in build.xml or its parent, build/build.xml. $ cvs diff build.xml Index: build.xml =================================================================== RCS file: /cvsroot/jbpm/jbpm.3/jpdl/dist/build.xml,v retrieving revision 1.22 diff -r1.22 build.xml 210c210 < <target name="test.suite.distribution" depends="clean, dist" description="test a suite distribution build"> --- > <target name="test.suite.distribution" depends="clean" description="test a suite distribution build"> -- 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

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-845) ransient variables between process and subprocess

by Harald Strack (JIRA)

ransient variables between process and subprocess ------------------------------------------------- Key: JBPM-845 URL: http://jira.jboss.com/jira/browse/JBPM-845 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.4, jBPM 3.1.3, jBPM 3.1.2, jBPM 3.1.1, jBPM 3.1 Reporter: Harald Strack Assigned To: Tom Baeyens Attachments: patch Hi, why is there not the same functionality for transient variables as for persistent ones when copying variables from a superprocess to a subprocess (process state)? I have seen this thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70407 The proposed solution as seen in jira http://jira.jboss.com/jira/browse/JBPM-399 is implemented in jbpm 3.1.2 that I am actually using. I think this solution is simple (and buggy: it only works when you also habe some persistent varibale mappings!) but does not fit for the most common case, that a superprocess calls a common suprocess and the subprocess does not know anything about the superprocess. More specific, there could be different superprocesses with different transient variable names. These superprocesses may call a general subprocess... Using the present solution forces the subprocess to know about all possible variablenames of all possible superprocesses - that's really bad! What we need is varible scoping. What can we do? Is it is not difficult to implement similar code for transient variables as you did for persistent ones. Patch for 3.1.3 and 3.1.4 following... -- 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

19 years, 3 months

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-903) Fetching a kind of "admin taskList", etc.

by Wolfgang Hollweck (JIRA)

Fetching a kind of "admin taskList", etc. ----------------------------------------- Key: JBPM-903 URL: http://jira.jboss.com/jira/browse/JBPM-903 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.4 Reporter: Wolfgang Hollweck Assigned To: Tom Baeyens Priority: Minor There should be generally more flexibility when fetchin taskLists: So, there's currently no possibility, to fetch an "admin taskList", i.e. a taskList containing all taskInstances, no matter which actor/pooledActors are assigned. The same's for fetching a taskList containing all taskInstances belonging to a certain processDefinition filtered (or not) by actor/pooledActors. By the way, I think there's no possibility to fetch taskInstances that have already ended from the DB. Maybe there are even more issues on fetching taskInstances that would be nice to have... -- 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

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-831) avoid using default id generator

by Wenbo Zhu (JIRA)

avoid using default id generator -------------------------------- Key: JBPM-831 URL: http://jira.jboss.com/jira/browse/JBPM-831 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.2 Environment: The problem is common to all platform. Issue is identifed on Oracle 9.1 specifically. Reporter: Wenbo Zhu Assigned To: Tom Baeyens The Id generator should be named explicitly, which is currently not. <id name="id" column="ID_"><generator class="native" /></id> This will introdcue issue when jbpm schema has to be updated (dropped, e.g.) as the db may be shared with other apps that uses default hibernate id generator too .. in case of Oracle, it's "hibernate_sequence". - Wenbo -- 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

19 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-891) db conversion script for timers

by Tom Baeyens (JIRA)

db conversion script for timers ------------------------------- Key: JBPM-891 URL: http://jira.jboss.com/jira/browse/JBPM-891 Project: JBoss jBPM Issue Type: Task Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2 i thought that there would be no db conversion necessary. only a schema update. but i think there is one conversion necessary in the db: timers. for messages, you can simply make sure that the webapp does not accept incoming requests and then leave the command executor running for a while till all async messages are processed. (that also needs to be documented) so we need to make a migration guide in the release notes of 3.2. The schema updates are already there (those need another update, but i can do that later). to be added is guidance on how to convert the timers. wether a conversion script and code is required, i don't know yet. please evaluate the strategies with me: 1) writing a conversion tool based on hibernate. The tool could just take the old Timer.hbm.xml and the new Job.hbm.xml, load from one table and insert in the other. all with the same session cause you can assume that the job table will be in the same db as the old jbpm tables. 2) we could also just give one or more sql statements on how to convert the timers into jobs. of course this will cause more problems with db compatibility. ... any other strategy ? -- 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

19 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-899) Put jBPM into public maven repository

by Alexey Kakunin (JIRA)

Put jBPM into public maven repository ------------------------------------- Key: JBPM-899 URL: http://jira.jboss.com/jira/browse/JBPM-899 Project: JBoss jBPM Issue Type: Feature Request Affects Versions: jBPM 3.1.4 Reporter: Alexey Kakunin Assigned To: Tom Baeyens Please, place jBPM into public maven2 repository (seems under jboss folder). It will allow easily use jBPM in maven2-based projects -- 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

19 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBPM-708) Version control of the process definition

by Aravind Kumar (JIRA)

Version control of the process definition ----------------------------------------- Key: JBPM-708 URL: http://jira.jboss.com/jira/browse/JBPM-708 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.1 Reporter: Aravind Kumar Assigned To: Tom Baeyens When working with jBPM in developement environment, there is no control over the version of the process-definition. Each time the server is restarted, a new version is deployed. The work around that I did: <boolean name="update-definition" value="false"/> this tag is included in the jbpm.cfg.xml & a check at JbpmContext.java: public void deployProcessDefinition(ProcessDefinition processDefinition) { if(JbpmConfiguration.Configs.getBoolean("update-definition")) { getGraphSession().deployProcessDefinition(processDefinition); } } This works fine for a single process defifnition. In case, there are multiple process definitions and some needs to be updates and some need not be. -- 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

19 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBPM-895) null pointer when create new sub process definition

by Tom Nguyen (JIRA)

null pointer when create new sub process definition --------------------------------------------------- Key: JBPM-895 URL: http://jira.jboss.com/jira/browse/JBPM-895 Project: JBoss jBPM Issue Type: Bug Components: BPEL Affects Versions: jBPM 3.1.3 Reporter: Tom Nguyen Assigned To: Tom Baeyens I have a problem with my process composition Exception happen when deploying process with sub process: public void deployProcessDefinition() { ProcessDefinition processDefinition = ProcessDefinition.parseXmlResource("main/processdefinition.xml"); ProcessInstance instance = new ProcessInstance(processDefinition); JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); try { jbpmContext.deployProcessDefinition(processDefinition); } finally { jbpmContext.close(); } } java.lang.NullPointerException: can't create a process instance when processDefinition is null at org.jbpm.graph.exe.ProcessInstance.<init>(ProcessInstance.java:87) at org.jbpm.graph.exe.Token.createSubProcessInstance(Token.java:571) at org.jbpm.graph.node.ProcessState.execute(ProcessState.java:109) at org.jbpm.graph.def.Node.enter(Node.java:316) <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.1" name="main"> <start-state name="start"> </start-state> <end-state name="end"></end-state> <process-state name="sub"> <sub-process name="sub"/> </process-state> </process-definition> This is my sub process: <?xml version="1.0" encoding="UTF-8"?> <process-definition xmlns="urn:jbpm.org:jpdl-3.1" name="sub"> <start-state name="start"> </start-state> <end-state name="end"></end-state> </process-definition> -- 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

19 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-894) EL implementation in jBPM does not find inherited methods

by Gavin King (JIRA)

EL implementation in jBPM does not find inherited methods ---------------------------------------------------------- Key: JBPM-894 URL: http://jira.jboss.com/jira/browse/JBPM-894 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Reporter: Gavin King Assigned To: Tom Baeyens Users report that EL in jBPM does not find methods/properties declared on superclasses. -- 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

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-892) Forgotten e.printStackTrace()

by Johan Parent (JIRA)

Forgotten e.printStackTrace() ----------------------------- Key: JBPM-892 URL: http://jira.jboss.com/jira/browse/JBPM-892 Project: JBoss jBPM Issue Type: Patch Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: XP, jbpm-3.1.4 Reporter: Johan Parent Assigned To: Tom Baeyens Priority: Trivial A forgotten stack trace in a catch block exposes an otherwise cought exception. Prevent elegant implementation of optimistic locking strategy. Patch is simple, remove line 213 in the close() methode in org.jbpm.svc.Service (for 3.1.4) -- 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

19 years, 3 months

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007