June 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2406) prune and document jpdl dependencies in pom

by Tom Baeyens (JIRA)

prune and document jpdl dependencies in pom ------------------------------------------- Key: JBPM-2406 URL: https://jira.jboss.org/jira/browse/JBPM-2406 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.1 currently there are too many dependencies. [INFO] ------------------------------------------------------------------------ [INFO] Building jBPM 4 - jPDL [INFO] task-segment: [dependency:tree] [INFO] ------------------------------------------------------------------------ [INFO] [dependency:tree] [INFO] org.jbpm.jbpm4:jbpm-jpdl:jar:4.0 [INFO] +- org.jbpm.jbpm4:jbpm-pvm:jar:4.0:compile [INFO] | +- org.jbpm.jbpm4:jbpm-api:jar:4.0:compile [INFO] | | \- jboss:jboss-j2ee:jar:4.2.2.GA:compile [INFO] | +- org.jbpm.jbpm4:jbpm-log:jar:4.0:compile [INFO] | +- org.jbpm.jbpm4:jbpm-test-base:jar:4.0:compile [INFO] | | \- org.hibernate:hibernate-core:jar:3.3.1.GA:compile [INFO] | | +- antlr:antlr:jar:2.7.6:compile [INFO] | | \- commons-collections:commons-collections:jar:3.1:compile [INFO] | +- org.apache.ant:ant:jar:1.7.0:compile [INFO] | | \- org.apache.ant:ant-launcher:jar:1.7.0:compile [INFO] | +- log4j:log4j:jar:1.2.14:compile [INFO] | +- juel:juel:jar:2.1.0:compile [INFO] | +- juel:juel-impl:jar:2.1.0:compile [INFO] | +- juel:juel-engine:jar:2.1.0:compile [INFO] | +- org.slf4j:slf4j-api:jar:1.5.2:compile [INFO] | +- org.slf4j:slf4j-jdk14:jar:1.5.2:compile [INFO] | +- org.jboss.identity.idm:idm-core:jar:1.0.0.Beta1:compile [INFO] | | +- org.jboss.identity.idm:idm-common:jar:1.0.0.Beta1:compile [INFO] | | +- org.jboss.identity.idm:idm-api:jar:1.0.0.Beta1:compile [INFO] | | +- org.jboss.identity.idm:idm-spi:jar:1.0.0.Beta1:compile [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.1.8:compile [INFO] | | \- javax.xml.bind:jaxb-api:jar:2.1:compile [INFO] | | \- javax.xml.stream:stax-api:jar:1.0-2:compile [INFO] | +- org.jboss.identity.idm:idm-hibernate:jar:1.0.0.Beta1:compile [INFO] | | +- javassist:javassist:jar:3.4.GA:compile [INFO] | | +- org.hibernate:hibernate-cglib-repack:jar:2.1_3:compile [INFO] | | \- org.slf4j:slf4j-log4j12:jar:1.5.2:compile [INFO] | +- org.hibernate:hibernate-entitymanager:jar:3.4.0.GA:compile [INFO] | | +- org.hibernate:ejb3-persistence:jar:1.0.2.GA:compile [INFO] | | +- org.hibernate:hibernate-commons-annotations:jar:3.1.0.GA:compile [INFO] | | +- org.hibernate:hibernate-annotations:jar:3.4.0.GA:compile [INFO] | | +- dom4j:dom4j:jar:1.6.1:compile [INFO] | | | \- xml-apis:xml-apis:jar:1.0.b2:compile [INFO] | | \- javax.transaction:jta:jar:1.1:compile [INFO] | +- org.livetribe:livetribe-jsr223:jar:2.0.5:compile [INFO] | \- javax.mail:mail:jar:1.4.1:compile [INFO] | \- javax.activation:activation:jar:1.1:compile [INFO] +- junit:junit:jar:3.8.1:compile [INFO] \- hsqldb:hsqldb:jar:1.8.0.7:test [INFO] ------------------------------------------------------------------------ -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2556) identify minimal runtime library dependencies

by Tom Baeyens (JIRA)

identify minimal runtime library dependencies --------------------------------------------- Key: JBPM-2556 URL: https://jira.jboss.org/jira/browse/JBPM-2556 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.x feedback from a customer: " after trying hard today, I got jBPM4 running in OSGi equinox. I only tested a little functionality with a simple persistent jPDL workflow using HSQL in-memory db. The problem was that the SAXFactory provider could not be configured properly and resulted in a classloader violation exception. Solution was actually simple: I removed all 3rd party libraries that have something to do with XML (e.g. xml-apis.jar) and ship with jBPM4 and from the bundle-classpath. Now I wonder, if the JBPM4 team has an overview of the necessary smallest dependency set for 3rd-party libs in order to OSGi-tify jBPM and these dependend-jars and get the unnecessary rubbish out of the classpath. Hope they can provide some feedback about that. ------------------ I forgot to send you my current MANIFEST which is working with the small example: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: WFTEST Bundle-SymbolicName: WFTEST Bundle-Version: 1.0.0.qualifier Bundle-Activator: wftest.Activator Bundle-ActivationPolicy: lazy Bundle-RequiredExecutionEnvironment: JavaSE-1.6 Import-Package: org.osgi.framework;version="1.3.0" Bundle-ClassPath: lib/activation.jar, lib/antlr.jar, lib/avalon-framework.jar, lib/commons-collections.jar, lib/commons-logging.jar, lib/dom4j.jar, lib/ejb3-persistence.jar, lib/hibernate-annotations.jar, lib/hibernate-cglib-repack.jar, lib/hibernate-commons-annotations.jar, lib/hibernate-core.jar, lib/hibernate-entitymanager.jar, lib/hsqldb.jar, lib/idm-api.jar, lib/idm-common.jar, lib/idm-core.jar, lib/idm-hibernate.jar, lib/idm-spi.jar, lib/javassist.jar, lib/jaxb-api.jar, lib/jaxb-impl.jar, lib/jboss-common-core.jar, lib/jboss-j2ee.jar, lib/jboss-logging-spi.jar, lib/jbosscache-core.jar, lib/jbpm-console-form-plugin.jar, lib/jbpm-console-graphView-plugin.jar, lib/jbpm-console-integration.jar, lib/jbpm-console-reports.jar, lib/jbpm-examples-tests.jar, lib/jbpm-jboss4.jar, lib/jbpm-jboss5.jar, lib/jbpm-spi.jar, lib/jbpm-test-db-tests.jar, lib/jbpm-tomcat6.jar, lib/jbpm.jar, lib/jgroups.jar, lib/jta.jar, lib/jtds.jar, lib/juel-engine.jar, lib/juel-impl.jar, lib/juel.jar, lib/junit.jar, lib/livetribe-jsr223.jar, lib/log4j.jar, lib/logkit.jar, lib/mail.jar, lib/mysql-connector-java.jar, lib/postgresql.jar, lib/servlet-api.jar, lib/slf4j-api.jar, lib/slf4j-jdk14.jar, lib/slf4j-log4j12.jar, lib/standalone-compiler.jar, lib/subethasmtp-smtp.jar, lib/subethasmtp-wiser.jar, . I guess several of these jars could be removed and the remaining could be wrapped in OSGi-Bundle jars. ------------------ " -- 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, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2550) jbpm 4.1 Fork and Join gives some exception. Details given belo

by Makarand Kulkarni (JIRA)

jbpm 4.1 Fork and Join gives some exception. Details given belo --------------------------------------------------------------- Key: JBPM-2550 URL: https://jira.jboss.org/jira/browse/JBPM-2550 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Environment: jbpm 4.1, jboss 5.0 and GPD designer with eclipse packaged with jbpm 4.1 Reporter: Makarand Kulkarni Fix For: jBPM 4.x Hi, JPDL ( SubProcessFill.jpdl )attached ( having fork,join with tasks ) with this ticket is giving following exception org.jboss.resteasy.spi.UnhandledException: org.hibernate.LazyInitializationException: could not initialize proxy - no Session Complete error stack is attached. --- One of my requirement is to assign task( taskform) to multiple users and wait in the process till all users completes the filling of task form. Tried subprocess but then taskform gets assigned to single user. Also tried candidategroups. Same problem here. Your help in this regard is highly appreciated. Waiting for your reply. -Regards Makarand -- 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, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2801) Support querying for Tasks by their executionId

by Per Christian Henden (JIRA)

Support querying for Tasks by their executionId ----------------------------------------------- Key: JBPM-2801 URL: https://jira.jboss.org/jira/browse/JBPM-2801 Project: jBPM Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: jBPM 4.x Reporter: Per Christian Henden Fix For: jBPM 4.x I have a case where I need to look up tasks in an EventListener. What's available to me is the EventListenerExecution (ExecutionImpl). I found no simple way of doing this. The attched patch adds the ability to query by executionId in a TaskQuery, exactly like in a HistoryTaskQuery. The simplest way to do this today (as far as I know) is: DbSession taskDbSession = EnvironmentImpl.getFromCurrent(DbSession.class); Task = taskDbSession.findTaskByExecution(execution); I dislike using the DbSession object this way, it would be better to use the JBPM API. Using HistoryTaskService (which is part of the API) is possible, but is too much work: //Find all tasks related to the current execution final List<HistoryTask> relatedTasks = processEngine.getHistoryService().createHistoryTaskQuery().executionId(execution.getId()).list(); //Find all active tasks of the current execution final List<HistoryTask> activeTasks = new ArrayList<HistoryTask>(); for (HistoryTask ht : relatedTasks) { if (ht.getState() == null) { activeTasks.add(ht); } } if (activeTasks.size() > 1) { throw new IllegalStateException("Got multiple matching tasks!"); } else if (activeTasks.isEmpty()) { throw new IllegalStateException("Got no matching tasks!"); } return activeTasks.get(0); With the new code: Task t = processEngine.getTaskService().createTaskQuery().executionId(execution).uniqueResult(); -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2697) split up devguide incubation chapter into multiple incubation chapters

by Tom Baeyens (JIRA)

split up devguide incubation chapter into multiple incubation chapters ---------------------------------------------------------------------- Key: JBPM-2697 URL: https://jira.jboss.org/jira/browse/JBPM-2697 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.4 The current incubation chapter in the dev guide is too big. So we must split it up. The most obvious way is to create multiple incubation chapters in the current dev guide. E.g. * Incubation: jPDL * Incubation: BPMN * Incubation: Instance migration * Incubation: Task forms * ... -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2772) EventListenerExection.getKey() always returns NULL for subprocesses.

by Martin Porter (JIRA)

EventListenerExection.getKey() always returns NULL for subprocesses. -------------------------------------------------------------------- Key: JBPM-2772 URL: https://jira.jboss.org/jira/browse/JBPM-2772 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Environment: All Reporter: Martin Porter It is not possible to retrieve the business key in an EventListener for a subprocess. The call to EventListenerExecition.getKey() always returns null. -- 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, 8 months

5
7
0 / 0

[JBoss JIRA] Created: (JBPM-2830) (BPMN) In Latest source jbpm uses the name instead of the id for processes

by Sebastian Rühl (JIRA)

(BPMN) In Latest source jbpm uses the name instead of the id for processes -------------------------------------------------------------------------- Key: JBPM-2830 URL: https://jira.jboss.org/jira/browse/JBPM-2830 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Sebastian Rühl In Latest source jbpm uses the name instead of the id for processes... In my opinion this is the wrong behaviour as the name of a process will be converted to a id. So if you want to start a process via: executionService.startProcessInstanceByKey("process4711") it will throw a exception. Example Process for this: <process id="process4711" name="Could be a very long description and is not used to IDENTIFY"> -- 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, 8 months

4
11
0 / 0

[JBoss JIRA] Created: (JBPM-1776) org.jbpm.calendar.BusinessCalendar.add(Date, Duration) delivers unexpected results when business amounts are subtracted

by JÃÂÃÂ¼rgen Lampe (JIRA)

org.jbpm.calendar.BusinessCalendar.add(Date, Duration) delivers unexpected results when business amounts are subtracted ----------------------------------------------------------------------------------------------------------------------- Key: JBPM-1776 URL: https://jira.jboss.org/jira/browse/JBPM-1776 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: API Affects Versions: jBPM 3.2.3 Environment: java.version 1.5.0_13 java.vm.version 1.5.0_13-b05 os.name Windows XP os.version 5.1 Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.0 Created-By: 1.7.0-b21 (Sun Microsystems Inc.) Implementation-Title: jBPM Core Library Implementation-Version: 3.2.3 (date:18-Jun-2008 00:51) Implementation-URL: http://www.jboss.org/ Implementation-Vendor: JBoss Inc. Implementation-Vendor-Id: http://www.jboss.org/ Reporter: JÃÂÃÂ¼rgen Lampe When subtracting business time amounts from a date, the result is after the date and not - as one would expect - before this date. Examples: Sat Nov 01 00:00:00 CET 2008 + 2 business days -> Tue Nov 04 17:00:00 CET 2008 - OK Sat Nov 01 00:00:00 CET 2008 - 2 business days -> Sun Nov 02 18:00:00 CET 2008 - unexpected Sat Nov 01 00:00:00 CET 2008 + 2 business hours -> Mon Nov 03 11:00:00 CET 2008 - OK Sat Nov 01 00:00:00 CET 2008 -2 business hours -> Mon Nov 03 07:00:00 CET 2008 - unexpected Data was created by use of small test program: Date date=new SimpleDateFormat("dd.MM.yyyy").parse("01.11.2008"); String[] durStrs= {"+ 2 business days", "- 2 business days", "+ 2 business hours", "-2 business hours"}; BusinessCalendar calendar= new BusinessCalendar(); for (String durStr: durStrs) { Duration duration= new Duration(durStr); Date d= calendar.add(date, duration); System.out.println(" "+date+" "+durStr+" -> "+d); } -- 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, 8 months

9
16
0 / 0

[JBoss JIRA] Created: (JBPM-2422) investigate if logging abstraction should be removed

by Tom Baeyens (JIRA)

investigate if logging abstraction should be removed ---------------------------------------------------- Key: JBPM-2422 URL: https://jira.jboss.org/jira/browse/JBPM-2422 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Priority: Minor Fix For: jBPM 4.x the current approach is to have a minimal log framework pluggability: ---------------------------------------------------------------------------------------------- 1) jdk logging because we want it to be possible to run pvm without external library dependencies 2) log4j as jboss doesn't include a jdklogging-to-log4j bridge. general links ------------------ http://www.jboss.org/community/wiki/Logging select between these options: ----------------------------------------- 1) always require a jbpm.logging.properties on the classpath. that configures the jdk logging. eithers completely, or with a delegation to log4j in that case our jbpm code can always use the jdk logging. 2) keep it as it is 3) similar solution to seam for facelets: ===http://markmail.org/message/ywamc5yc7hejrlls==================================================================== Subject: Facelets JDK Logging -> JBoss Log4j bridge Actions... From: Pete Muir (pmu...(a)bleepbleep.org.uk) Date: Feb 19, 2008 7:27:50 am List: net.java.dev.facelets.dev As has been discussed many times on the seam forum and facelets mailing list, JBoss AS doesn't have a jdk logger -> log4j generic bridge (I don't know why, and I don't really want to find out) so what Stan did for JSF RI was write a JDK logging filter that would bridge JUL to log4j. I have done the same for Facelets (included as part of jboss-seam-ui.jar, I can factor out the relevant code if anyone wants it) but hit a sight problem. Most logs in facelets are declared protected static final (so I can get at them using reflection) but in DefaultFacelet, CompositionHandler and DecorateHandler they are protected final (so I can't get at them easily as they aren't static). Any chance they could become static? Let me know and I'll file a bug. Code is here http://fisheye.jboss.org/browse/Seam/trunk/ui/src/main/java/org/jboss/sea... Thanks, Pete -- Pete Muir http://in.relation.to/Bloggers/Pete http://www.seamframework.org ============================================================================================================ -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2688) extend ProcessInstanceQuery so that process instances can be searched by their processDefinitionKeys

by Sebastian Schneider (JIRA)

extend ProcessInstanceQuery so that process instances can be searched by their processDefinitionKeys ---------------------------------------------------------------------------------------------------- Key: JBPM-2688 URL: https://jira.jboss.org/jira/browse/JBPM-2688 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.2 Reporter: Sebastian Schneider When using a ProcessInstanceQuery it is possible to search by processBusinessKey and also by processDefinitionId. The ProcessInstanceQuery should be extended so that process instances can also be searched by processDefinitionKeys. This is usel in situations where you want to retrieve all process instances of the same process definition but in different versions. -- 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, 9 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2010