June 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1994) Provide process execution logging

by Heiko Braun (JIRA)

Provide process execution logging --------------------------------- Key: JBPM-1994 URL: https://jira.jboss.org/jira/browse/JBPM-1994 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.0.Beta2 Reporter: Heiko Braun Transactional storage of the history of a process execution (not software logging) Log pluggability is in place Basic pluggability infrastructure is in place HistoryRecords generated during process execution need to be created HistoryRecords need to merge themselves into the History DB schema Schema for storing history information needs to be build Filtering the history storage should be based on features We should not place the burden on the users to link log filtering to the features that remain available -- 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, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-2373) add task history

by Tom Baeyens (JIRA)

add task history ---------------- Key: JBPM-2373 URL: https://jira.jboss.org/jira/browse/JBPM-2373 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.x currently only task acitivity instances are stored in the history. in other words only tasks that are associated to an execution have history information. this issue means that also standalone tasks, dynamically created with the api, should have history as well. we (joram and me 30/06/2009) think that it's best to add a separate task history table for that purpose. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-1292) Integrate simulation tests in automated testrun

by Thomas Diesler (JIRA)

Integrate simulation tests in automated testrun ----------------------------------------------- Key: JBPM-1292 URL: http://jira.jboss.com/jira/browse/JBPM-1292 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM jPDL 3.2.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

15 years, 5 months

4
24
0 / 0

[JBoss JIRA] Created: (JBPM-2321) Error while fetching latest version

by sri r (JIRA)

Error while fetching latest version ------------------------------------ Key: JBPM-2321 URL: https://jira.jboss.org/jira/browse/JBPM-2321 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.CR1 Reporter: sri r The query generated for the below statement results in two records causing below error. Basically i'm trying to check the latest version deployed so as to proceed with deploying a newer version of process definition xml. repositorySession .createProcessDefinitionQuery() .processDefinitionKey(key) .orderDesc(ProcessDefinitionQuery.PROPERTY_VERSION) .page(0, 1) .uniqueResult(); Caused by: org.jbpm.api.JbpmException: result not unique: 2 at org.jbpm.pvm.internal.query.AbstractQuery.untypedUniqueResult(AbstractQuery.java:81) at org.jbpm.pvm.internal.query.ProcessDefinitionQueryImpl.uniqueResult(ProcessDefinitionQueryImpl.java:151) Queries: Hibernate: select deployment1_.OBJNAME_ as col_0_0_, deployment1_.DEPLOYMENT_ as col_1_0_ from public.JBPM4_DEPLOYMENT deployment0_, public.JBPM4_DEPLOYPROP deployment1_, public.JBPM4_DEPLOYPROP deployment2_, public.JBPM4_DEPLOYPROP deployment3_ where deployment0_.STATE_<>'suspended' and deployment1_.KEY_='pdid' and deployment1_.DEPLOYMENT_=deployment0_.DBID_ and deployment2_.KEY_='pdkey' and deployment2_.OBJNAME_=deployment1_.OBJNAME_ and deployment2_.DEPLOYMENT_=deployment0_.DBID_ and deployment3_.KEY_='pdversion' and deployment3_.OBJNAME_=deployment1_.OBJNAME_ and deployment3_.DEPLOYMENT_=deployment0_.DBID_ and deployment1_.OBJNAME_=? Hibernate: select deployment0_.DBID_ as DBID1_10_0_, deployment0_.NAME_ as NAME2_10_0_, deployment0_.TIMESTAMP_ as TIMESTAMP3_10_0_, deployment0_.STATE_ as STATE4_10_0_ from public.JBPM4_DEPLOYMENT deployment0_ where deployment0_.DBID_=? Hibernate: select resources0_.DEPLOYMENT_ as DEPLOYMENT7_1_, resources0_.DBID_ as DBID1_1_, resources0_.NAME_ as NAME8_1_, resources0_.DBID_ as DBID1_3_0_, resources0_.DBVERSION_ as DBVERSION2_3_0_, resources0_.BLOB_VALUE_ as BLOB3_3_0_, resources0_.BINARY_VALUE_ as BINARY4_3_0_, resources0_.CLOB_VALUE_ as CLOB5_3_0_, resources0_.TEXT_VALUE_ as TEXT6_3_0_ from public.JBPM4_LOB resources0_ where resources0_.DEPLOYMENT_=? Hibernate: select objectprop0_.DEPLOYMENT_ as DEPLOYMENT2_1_, objectprop0_.DBID_ as DBID1_1_, objectprop0_.DBID_ as DBID1_11_0_, objectprop0_.DEPLOYMENT_ as DEPLOYMENT2_11_0_, objectprop0_.OBJNAME_ as OBJNAME3_11_0_, objectprop0_.KEY_ as KEY4_11_0_, objectprop0_.STRINGVAL_ as STRINGVAL5_11_0_, objectprop0_.LONGVAL_ as LONGVAL6_11_0_ from public.JBPM4_DEPLOYPROP objectprop0_ where objectprop0_.DEPLOYMENT_=? Hibernate: select deployment0_.DBID_ as DBID1_10_0_, deployment0_.NAME_ as NAME2_10_0_, deployment0_.TIMESTAMP_ as TIMESTAMP3_10_0_, deployment0_.STATE_ as STATE4_10_0_ from public.JBPM4_DEPLOYMENT deployment0_ where deployment0_.DBID_=? Hibernate: select resources0_.DEPLOYMENT_ as DEPLOYMENT7_1_, resources0_.DBID_ as DBID1_1_, resources0_.NAME_ as NAME8_1_, resources0_.DBID_ as DBID1_3_0_, resources0_.DBVERSION_ as DBVERSION2_3_0_, resources0_.BLOB_VALUE_ as BLOB3_3_0_, resources0_.BINARY_VALUE_ as BINARY4_3_0_, resources0_.CLOB_VALUE_ as CLOB5_3_0_, resources0_.TEXT_VALUE_ as TEXT6_3_0_ from public.JBPM4_LOB resources0_ where resources0_.DEPLOYMENT_=? Hibernate: select objectprop0_.DEPLOYMENT_ as DEPLOYMENT2_1_, objectprop0_.DBID_ as DBID1_1_, objectprop0_.DBID_ as DBID1_11_0_, objectprop0_.DEPLOYMENT_ as DEPLOYMENT2_11_0_, objectprop0_.OBJNAME_ as OBJNAME3_11_0_, objectprop0_.KEY_ as KEY4_11_0_, objectprop0_.STRINGVAL_ as STRINGVAL5_11_0_, objectprop0_.LONGVAL_ as LONGVAL6_11_0_ from public.JBPM4_DEPLOYPROP objectprop0_ where objectprop0_.DEPLOYMENT_=? -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2320) populate name attribute in Deployment while parsing xml file

by sri r (JIRA)

populate name attribute in Deployment while parsing xml file ------------------------------------------------------------ Key: JBPM-2320 URL: https://jira.jboss.org/jira/browse/JBPM-2320 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.CR1 Reporter: sri r Hi, In jBPM 3.x, we had a way to check if a version of process defintiion is already deployed by checking it against the name (name attribute from process definition.xml). With jBPM 4.x, deployment.addResourceFromClasspath(fileName) populates DeploymentImpl object with name attribute being null in it.. As a result, only way for end applications is to work around by comparing filename for ex. Instead if addResourceFromClasspath populates name attribute, we can directly query based on it. Noticed that jbpm 4 loads the deployment info into a hashmap with filename, lob object into resource service. resources.put(name, lob); -- 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, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBPM-2354) fix excluded integration tests for test-db

by Tom Baeyens (JIRA)

fix excluded integration tests for test-db ------------------------------------------ Key: JBPM-2354 URL: https://jira.jboss.org/jira/browse/JBPM-2354 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.0 in the test-db pom: <plugin> <artifactId>maven-surefire-plugin</artifactId> <configuration> <failIfNoTests>false</failIfNoTests> <trimStackTrace>false</trimStackTrace> <excludes> <exclude>org/jbpm/test/activities/ForkJoinInSameTransactionTest.java</exclude> <exclude>org/jbpm/test/execution/ConcurrentEndTest.java</exclude> <exclude>org/jbpm/test/async/AsyncEndCombinationTest.java</exclude> <exclude>reporting/SQLStmtTest.java</exclude> </excludes> </configuration> </plugin> -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2195) rename gwt-console to jbpm-console

by Tom Baeyens (JIRA)

rename gwt-console to jbpm-console ---------------------------------- Key: JBPM-2195 URL: https://jira.jboss.org/jira/browse/JBPM-2195 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Heiko Braun Fix For: jBPM 4.0.0.CR1 -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2372) complete javadocs

by Tom Baeyens (JIRA)

complete javadocs ----------------- Key: JBPM-2372 URL: https://jira.jboss.org/jira/browse/JBPM-2372 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.0 -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPM-2336) fix delete task mismatch

by Tom Baeyens (JIRA)

fix delete task mismatch ------------------------ Key: JBPM-2336 URL: https://jira.jboss.org/jira/browse/JBPM-2336 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 task service interface delete task is translated in the impl to cancel. this ripples through to the task handler interface. should be made more consistent -- 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, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPM-2306) fix developers guide

by Tom Baeyens (JIRA)

fix developers guide -------------------- Key: JBPM-2306 URL: https://jira.jboss.org/jira/browse/JBPM-2306 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.0 -- 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, 5 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2009