September 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2519) jbpm4 user guide : wrong location for the GPD plugin

by Nicolas Pirard (JIRA)

jbpm4 user guide : wrong location for the GPD plugin ---------------------------------------------------- Key: JBPM-2519 URL: https://jira.jboss.org/jira/browse/JBPM-2519 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: GPD Affects Versions: jBPM 4.1 Reporter: Nicolas Pirard I did not find the subdirectory gpd when unzipping the jbpm-4.1.zip , whereas it was present in the 4.0 version. (and is referred to in the 4.1 doc jbpm-4.1/doc/userguide/html_single/index.html#graphicalprocessdesigner) Is it elsewhere now? ---> yes , it is in jbpm-4.1\install\src\gpd could someone udpate the doc? Maybe it can be fixed "on-the-fly" without waiting for a real release? after all it is only a text document, no possible side effect on the code link to forum topic : http://www.jboss.org/index.html?module=bb&op=viewtopic&t=160731 -- 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

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2520) The install build.xml is not reporting the new Signavio installtion target (patch attached)

by eric schabell (JIRA)

The install build.xml is not reporting the new Signavio installtion target (patch attached) ------------------------------------------------------------------------------------------- Key: JBPM-2520 URL: https://jira.jboss.org/jira/browse/JBPM-2520 Project: jBPM Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: jBPM 4.1 Environment: Fedora 11, x86_64, java (sun) 1.6.0_14, apache-ant 1.7.1 Reporter: eric schabell Priority: Trivial Fix For: jBPM 4.2 The new web console installation targets (jboss and tomcat) are not listed in the ant -p output. This installation is mentioned in the user guides but needs to be added to the build.xml. Only need to add a description to get this to work. Will supply patch. -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2511) move tmp directory of signavio installation to install/generated

by Tom Baeyens (JIRA)

move tmp directory of signavio installation to install/generated ---------------------------------------------------------------- Key: JBPM-2511 URL: https://jira.jboss.org/jira/browse/JBPM-2511 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Joram Barrez Fix For: jBPM 4.2 while installing signavio, this is logged internal.set.signavio.repo.dir: [mkdir] Created dir: c:\software\jbpm-4.1\signavio-repository [mkdir] Created dir: c:\software\jbpm-4.1\temp-signavio-unzip [unzip] Expanding: c:\software\jbpm-4.1\install\src\signavio\jbpmeditor.war into c:\software\jbpm-4.1\temp-signavio-unzip [zip] Building zip: c:\software\jbpm-4.1\temp-signavio-unzip\jbpmeditor.war the temporary location should become install/generated/signavio-tmp -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2507) org.jbpm.integration.console.ModelAdaptor adoptTask does not copy over the task description

by Robert Moskal (JIRA)

org.jbpm.integration.console.ModelAdaptor adoptTask does not copy over the task description ------------------------------------------------------------------------------------------- Key: JBPM-2507 URL: https://jira.jboss.org/jira/browse/JBPM-2507 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Reporter: Robert Moskal No where do we get from the Task passed in and assign it to the TaskRef -- 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

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2502) Queries ignore order by

by Hauke Rabe (JIRA)

Queries ignore order by ----------------------- Key: JBPM-2502 URL: https://jira.jboss.org/jira/browse/JBPM-2502 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.0 Reporter: Hauke Rabe Priority: Critical Missing method call to org.jbpm.pvm.internal.queryAbstractQuery#appendOrderByClause(StringBuilder hql). Only TaskQueryImpl, ProcessDefinitionQueryImpl and ProcessInstanceQueryImpl call org.jbpm.pvm.internal.queryAbstractQuery#appendOrderByClause(StringBuilder hql). But all define the orderAsc / orderDesc methods. -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2504) TaskQuery has wrong / missing property constants

by Hauke Rabe (JIRA)

TaskQuery has wrong / missing property constants ------------------------------------------------ Key: JBPM-2504 URL: https://jira.jboss.org/jira/browse/JBPM-2504 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Reporter: Hauke Rabe Priority: Critical TaskQuery #PROPERTY_CREATEDATE = "create" <> jbpm.task.hbm.xml property name="createTime" Also some properties are missing, like "state" TaskQuery is not the only interface of that kind, extend and correct although other Query interfaces. -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBPM-2527) introduce schema version property

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2527?page=com.atlassian.jira.plug... ] Tom Baeyens resolved JBPM-2527. ------------------------------- Fix Version/s: (was: jBPM 4.2) Resolution: Duplicate Issue included into implementation of key generation: JBPM-2526 > introduce schema version property > --------------------------------- > > Key: JBPM-2527 > URL: https://jira.jboss.org/jira/browse/JBPM-2527 > Project: jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Tom Baeyens > > Introduce table JBPM4_PROPERTIES > Initialize a property called SCHEMAVERSION that reflects the version of the jBPM schema. At startup, the process engine should verify/validate this property and later potentially perform DB upgrades automatically. -- 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

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-2526) implement jbpm key generation

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2526?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-2526: ----------------------------------- introduce JBPM4_PROPERTIES and schema version property used to be a separate issue : JBPM-2527 > implement jbpm key generation > ----------------------------- > > Key: JBPM-2526 > URL: https://jira.jboss.org/jira/browse/JBPM-2526 > Project: jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Priority: Critical > Fix For: jBPM 4.2 > > > mechanism: > 1) add JBPM4_PROPERTIES table (See also JBPM-2527) > 2) define a property called NEXTID with a long value that is initialized at 1 > 3) define a KeyGeneratorImpl in the process-engine context, with eager initialization > 4) make sure that all hibernate entities during construction get a value from the id generator > - each id generator will acquire a block of ids by updating the NEXTID property > - block acquisition is guarded with optimistic locking > - ids will be consumed from the block (very fast, without db access) > 5) remove all the explicit flushes > 6) implement a DefaultKeyGenerator that only uses in memory key generation in case people work without persistence > public abstract class KeyGenerator { > // similar as ScriptManager > public static KeyGenerator getKeyGenerator() {...} > // similar as ScriptManager > public static KeyGenerator getDefaultKeyGenerator() {...} > public long getNextId() {...} > } > Motivations: > 1) database portability : see also JBPM-2510 > 2) performance > JBPM-2510 -- 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

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-2526) implement jbpm key generation

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2526?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-2526: ------------------------------ Original Estimate: 1 week Remaining Estimate: 1 week > implement jbpm key generation > ----------------------------- > > Key: JBPM-2526 > URL: https://jira.jboss.org/jira/browse/JBPM-2526 > Project: jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Priority: Critical > Fix For: jBPM 4.2 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > mechanism: > 1) add JBPM4_PROPERTIES table (See also JBPM-2527) > 2) define a property called NEXTID with a long value that is initialized at 1 > 3) define a KeyGeneratorImpl in the process-engine context, with eager initialization > 4) make sure that all hibernate entities during construction get a value from the id generator > - each id generator will acquire a block of ids by updating the NEXTID property > - block acquisition is guarded with optimistic locking > - ids will be consumed from the block (very fast, without db access) > 5) remove all the explicit flushes > 6) implement a DefaultKeyGenerator that only uses in memory key generation in case people work without persistence > public abstract class KeyGenerator { > // similar as ScriptManager > public static KeyGenerator getKeyGenerator() {...} > // similar as ScriptManager > public static KeyGenerator getDefaultKeyGenerator() {...} > public long getNextId() {...} > } > Motivations: > 1) database portability : see also JBPM-2510 > 2) performance > JBPM-2510 -- 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

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPM-2527) introduce schema version property

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2527?page=com.atlassian.jira.plug... ] Tom Baeyens reassigned JBPM-2527: --------------------------------- Assignee: Tom Baeyens (was: Joram Barrez) > introduce schema version property > --------------------------------- > > Key: JBPM-2527 > URL: https://jira.jboss.org/jira/browse/JBPM-2527 > Project: jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Fix For: jBPM 4.2 > > > Introduce table JBPM4_PROPERTIES > Initialize a property called SCHEMAVERSION that reflects the version of the jBPM schema. At startup, the process engine should verify/validate this property and later potentially perform DB upgrades automatically. -- 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

15 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues September 2009