June 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2341) change swimlane assignee memory

by Tom Baeyens (JIRA)

change swimlane assignee memory ------------------------------- Key: JBPM-2341 URL: https://jira.jboss.org/jira/browse/JBPM-2341 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 now a swimlane will remember the actual assignee and use that for subsequent tasks. the default should be switched to *not* remembering the assignee. and reassign every task from scratch. e.g. to the group. an attribute should be introduced to activate remembering if the assignee that took on a task that was assigned to a group. -- 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, 1 month

4
11
0 / 0

[JBoss JIRA] Created: (JBPM-2203) seam integration

by Tom Baeyens (JIRA)

seam integration ---------------- Key: JBPM-2203 URL: https://jira.jboss.org/jira/browse/JBPM-2203 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0.CR1 help pete with seam integration -- 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, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBPM-2270) add ESB integration

by Tom Baeyens (JIRA)

add ESB integration ------------------- Key: JBPM-2270 URL: https://jira.jboss.org/jira/browse/JBPM-2270 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: GPD, Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1879) define node extension mechanism

by Tom Baeyens (JIRA)

define node extension mechanism ------------------------------- Key: JBPM-1879 URL: https://jira.jboss.org/jira/browse/JBPM-1879 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 Go over all aspects on how users can add nodes: * xsd: check out if substitution groups can play a role in this * persistence * parsing * graph designer - properties and matching them to the jpdl-xml attributes/elements for that node type matching the parsing - figure - icon * modelling constraints like e.g. max 1 outgoing flow -- 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, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-2310) introduce load testing

by Tom Baeyens (JIRA)

introduce load testing ---------------------- Key: JBPM-2310 URL: https://jira.jboss.org/jira/browse/JBPM-2310 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 -- 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, 2 months

4
9
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

14 years, 2 months

9
16
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

14 years, 2 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

14 years, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBPM-1768) fix groovy expression support

by Tom Baeyens (JIRA)

fix groovy expression support ----------------------------- Key: JBPM-1768 URL: https://jira.jboss.org/jira/browse/JBPM-1768 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 Fix test GroovyExpressionTest It's a matter of getting the right dependencies defined in maven. -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1775) verify if collection exceptionHandlers can be loaded lazy

by Tom Baeyens (JIRA)

verify if collection exceptionHandlers can be loaded lazy --------------------------------------------------------- Key: JBPM-1775 URL: https://jira.jboss.org/jira/browse/JBPM-1775 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 3.3.1 GA >From Martin Putz: " A quick test showed that setting all those relations to lazy="true" cuts down the number of executed SQL selects quite drastically. I don't see any negative side effects of changing these settings, but I'm curious about the reasons why lazy="false" is chosen as default. Especially as I don't see a lot of our customers using exception handlers (or at least they don't report it). Regards, Martin " -- 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, 5 months

5
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2009