June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Assigned: (JBPM-751) unnecessary warning on valid process definition

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-751?page=all ] Tom Baeyens reassigned JBPM-751: -------------------------------- Assignee: Koen Aers (was: Tom Baeyens) > unnecessary warning on valid process definition > ----------------------------------------------- > > Key: JBPM-751 > URL: http://jira.jboss.com/jira/browse/JBPM-751 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2, jBPM 3.1.2, jBPM 3.1.3, jBPM 3.1.4, jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Alex Burgel > Assigned To: Koen Aers > Priority: Minor > Fix For: jBPM jPDL 3.2.3, jBPM 3.2.2 SOA 1 > > > i get this warning: > process xml warning: warning: no swimlane or assignment specified for task '<task xmlns="urn:jbpm.org:jpdl-3.1" name="schedule" blocking="false" signalling="true" priority="normal"/>' > it seems a bit odd to generate a warning on a valid process definition. > i think it should either be illegal to have a task without an assignment or swimlane, or there shouldn't be any warning at all (maybe lower the logging level to INFO). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-751) unnecessary warning on valid process definition

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-751?page=all ] Tom Baeyens updated JBPM-751: ----------------------------- Fix Version/s: jBPM jPDL 3.2.3 jBPM 3.2.2 SOA 1 Priority: Minor (was: Trivial) > unnecessary warning on valid process definition > ----------------------------------------------- > > Key: JBPM-751 > URL: http://jira.jboss.com/jira/browse/JBPM-751 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2, jBPM 3.1.2, jBPM 3.1.3, jBPM 3.1.4, jBPM jPDL 3.2.1, jBPM jPDL 3.2.2 > Reporter: Alex Burgel > Assigned To: Tom Baeyens > Priority: Minor > Fix For: jBPM jPDL 3.2.3, jBPM 3.2.2 SOA 1 > > > i get this warning: > process xml warning: warning: no swimlane or assignment specified for task '<task xmlns="urn:jbpm.org:jpdl-3.1" name="schedule" blocking="false" signalling="true" priority="normal"/>' > it seems a bit odd to generate a warning on a valid process definition. > i think it should either be illegal to have a task without an assignment or swimlane, or there shouldn't be any warning at all (maybe lower the logging level to INFO). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-71) named variable declaration

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-71?page=all ] Tom Baeyens closed JBPM-71. --------------------------- Resolution: Deferred already done on the PVM > named variable declaration > -------------------------- > > Key: JBPM-71 > URL: http://jira.jboss.com/jira/browse/JBPM-71 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Optional > > add support for specifying how variables should be persisted on the basis of the name of the variable. > currently, we only support type determination on the basis of value-reflection. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-166) log level configuration

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-166?page=all ] Tom Baeyens closed JBPM-166. ---------------------------- Resolution: Deferred Postponed to jPDL 4: See PVM-46 > log level configuration > ----------------------- > > Key: JBPM-166 > URL: http://jira.jboss.com/jira/browse/JBPM-166 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Minor > > add support for logging configurations. one part of this is to enable/disable process logging for a jbpm installation (see other issue). another part is the addition of LoggingDefinition information that allows more fine grained control over which logs are maintained and which will be ignored. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-319) Addition of deployment date and getting a process definition using its deployment date

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-319?page=all ] Tom Baeyens closed JBPM-319. ---------------------------- Resolution: Deferred will be fixed in jPDL 4: see PVM-45 > Addition of deployment date and getting a process definition using its deployment date > -------------------------------------------------------------------------------------- > > Key: JBPM-319 > URL: http://jira.jboss.com/jira/browse/JBPM-319 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.0 > Environment: N/A > Reporter: Sultan Mahmood > Assigned To: Tom Baeyens > Priority: Minor > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > When a process is deployed its deployment date and activation date (when it can be used) should be saved. Later on i can get a process definition using its deployment/activation date. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-589) Add undo support

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-589?page=all ] Tom Baeyens closed JBPM-589. ---------------------------- Resolution: Won't Fix i don't think this can be done in a decent way, without side effects. it's possible to revert the node pointer and variable values. but what about all the other properties on token, process instance and so on. many properties can be updated without a log being produced > Add undo support > ---------------- > > Key: JBPM-589 > URL: http://jira.jboss.com/jira/browse/JBPM-589 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-420) jboss integration improvements

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-420?page=all ] Tom Baeyens closed JBPM-420. ---------------------------- Resolution: Deferred deferred to jpdl 4 > jboss integration improvements > ------------------------------ > > Key: JBPM-420 > URL: http://jira.jboss.com/jira/browse/JBPM-420 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > good mbean idea: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3902214#3902214 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1024) Serializable variables are not being deserialized when retrieved from process

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1024?page=comments#action_12415694 ] Tom Baeyens commented on JBPM-1024: ----------------------------------- Koen, can you verify the test and make sure it is on both the SOA branch and HEAD ? > Serializable variables are not being deserialized when retrieved from process > ----------------------------------------------------------------------------- > > Key: JBPM-1024 > URL: http://jira.jboss.com/jira/browse/JBPM-1024 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.4, jBPM jPDL 3.2.2 > Reporter: thilker > Assigned To: Alejandro Guizar > Fix For: jBPM jPDL 3.2.3 > > > Storing an serializable object in a process should write an "R" in the column "converter" in table JBPM_VARIABLEINSTANCE. > But the value of the field is "null". > The cause: > The converter ID is retrieved in class org.jbpm.db.hibernate.Converter at line 63. > For the case of the SerializableToByteArrayConverter the ID is "null". > Regards, > Thorsten -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1184) add end-task attribute to schema

by Tom Baeyens (JIRA)

add end-task attribute to schema -------------------------------- Key: JBPM-1184 URL: http://jira.jboss.com/jira/browse/JBPM-1184 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.3 the attribute that indicates if the process instance should be stopped or just the token, is not in the schema. -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1186) jobexecutor (threads) not stopped when JobExecutorServlet is destroyed

by Ronald van Kuijk (JIRA)

jobexecutor (threads) not stopped when JobExecutorServlet is destroyed ---------------------------------------------------------------------- Key: JBPM-1186 URL: http://jira.jboss.com/jira/browse/JBPM-1186 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.3 According to the javadoc of the jobexecutor servlet: /** * starts the job executor on init and closes the * jbpm configuration upon destroy. The closing of the * jbpm configuration will also shut down the job executor * thread pool. There is no destroy method, so nothing wil happen. Threads keep running. Secondly, I'm not sure closing the jBPM context is what we want there. Can't we just call jobExecutor.stop()? In case we just want to stop it? A stop/start method on the servlet with a param is also handy.... e.g. from the webconsole???? -- 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, 11 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 2008