October 2009 - jbpm-issues - Jboss List Archives

[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, 7 months

3
6
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, 7 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2069) IntegerToLongConverter not consistent when dealing with null-values

by Hans Huber (JIRA)

IntegerToLongConverter not consistent when dealing with null-values ------------------------------------------------------------------- Key: JBPM-2069 URL: https://jira.jboss.org/jira/browse/JBPM-2069 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.5 GA Reporter: Hans Huber Priority: Minor org.jbpm.context.exe.converter.IntegerToLongConverter.supports(Object) return true for null values. org.jbpm.context.exe.converter.IntegerToLongConverter.convert(Object) on the other hand throws a NPE when a null value is passed in. i found this inconsistency when i tried to null a previously set variable with executionContext.setVariable("foobar", new Long(1)); executionContext.setVariable("foobar", 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, 7 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-1992) Logging is missing if JobExecutorThread marks TX as rollbackonly because of max

by Roman Heinz (JIRA)

Logging is missing if JobExecutorThread marks TX as rollbackonly because of max ------------------------------------------------------------------------------- Key: JBPM-1992 URL: https://jira.jboss.org/jira/browse/JBPM-1992 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA Reporter: Roman Heinz If the execution of an action/script/... takes longer than the time configured org.jbpm.job.executor.JobExecutor.maxLockTime, the current TX is marked as rollback-only without any logging. In JobExecutorThread: // if this job is locked too long long totalLockTimeInMillis = System.currentTimeMillis() - job.getLockTime().getTime(); if (totalLockTimeInMillis>maxLockTime) { jbpmContext.setRollbackOnly(); } Logging is missing to inform about the jbpmContext.setRollbackOnly() together with the reason. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBPM-2398) expose full history details through the history api

by Tom Baeyens (JIRA)

expose full history details through the history api --------------------------------------------------- Key: JBPM-2398 URL: https://jira.jboss.org/jira/browse/JBPM-2398 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 expose the history that is in the database through the api -- 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
25
0 / 0

[JBoss JIRA] Created: (JBPM-2417) allow for programmatic way to specify authentication through service api

by Tom Baeyens (JIRA)

allow for programmatic way to specify authentication through service api ------------------------------------------------------------------------ Key: JBPM-2417 URL: https://jira.jboss.org/jira/browse/JBPM-2417 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 first target is our own console. our own console should pass the authentication information through the api. maybe this can be part of the more general: User provided transactional resources -- 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
9
0 / 0

[JBoss JIRA] Created: (JBPM-2568) review history based on user feedback

by Tom Baeyens (JIRA)

review history based on user feedback ------------------------------------- Key: JBPM-2568 URL: https://jira.jboss.org/jira/browse/JBPM-2568 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.3 Ronald mentioned a lot of questions and activity around history. This issue is a reminder that we have to look into this topic in the 4.3 jira period (1st half of november) https://jira.jboss.org/jira/sr/jira.issueviews:searchrequest-printable/te... We should try to get an overview of what exactly the history related questions/issues are and find out how we can address them. Then translate that into concrete jira issues that can be prioritized. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBPM-2442) Review task history details and add new information where needed

by Joram Barrez (JIRA)

Review task history details and add new information where needed ---------------------------------------------------------------- Key: JBPM-2442 URL: https://jira.jboss.org/jira/browse/JBPM-2442 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Joram Barrez Priority: Minor Fix For: jBPM 4.x See forum reference (assignment history). Check if there are other events that need to be logged. -- 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

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-2473) description about coexistence of version and binding attribute for sub-process is wrong

by Toshiya Kobayashi (JIRA)

description about coexistence of version and binding attribute for sub-process is wrong ---------------------------------------------------------------------------------------- Key: JBPM-2473 URL: https://jira.jboss.org/jira/browse/JBPM-2473 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.5.SP5 Reporter: Toshiya Kobayashi Priority: Minor 21.4.28. sub-process When both version and binding="late" are given then jBPM will use the version as requested, but will not yet try to find the sub process when the parent process-state is deployed. http://docs.jboss.org/jbpm/v3.2/userguide/html_single/index.html#subproce... But actually, ProcessState.execute() ignores version attribute if binding="late". So fix the description to: When both version and binding="late" are given then jBPM will ignore the version attribute and use the latest version. -- 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
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2009