May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Reopened: (JBPM-578) remove JbpmSession and JbpmSessionFactory

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-578?page=all ] Tom Baeyens reopened JBPM-578: ------------------------------ > remove JbpmSession and JbpmSessionFactory > ----------------------------------------- > > Key: JBPM-578 > URL: http://jira.jboss.com/jira/browse/JBPM-578 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM 4.0 > > > those are deprecated in jbpm 3.1 and will be removed in 3.2 -- 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-165) process instance versioning

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-165?page=all ] Tom Baeyens updated JBPM-165: ----------------------------- Fix Version/s: jBPM jPDL 3.2.2 (was: jBPM jPDL 3.2.1) i'm postponing this to 3.2.2 cause there are a lot of fixes waiting to be released > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: http://jira.jboss.com/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.2 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. -- 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-165) process instance versioning

by Tom Baeyens (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-165?page=comments#action_12363694 ] Tom Baeyens commented on JBPM-165: ---------------------------------- how do you handle the bidirectional reference between the old and the new process instance version ? > process instance versioning > --------------------------- > > Key: JBPM-165 > URL: http://jira.jboss.com/jira/browse/JBPM-165 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.1 > > > i think jbpm could offer some degree of assistence in process instance versioning. > when a new version of a process is deployed, jbpm could do the following conversion for a process instance : > * input required: mapping of the nodes from the old to the new definition. > * cancel the old process instance > * create a new process instance and copy the runtime (exe) information such as tokens and process variables from the old process instance. > * then establish a special link between the 2 process instances to indicate that the new process instance is the continuation of the old process instance. > this way we can avoid the problematic conversion of logs, while still keeping them in the system. -- 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

19 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-952) api support for finding the relationship of a process definition to an actor or to pooledActors

by y o (JIRA)

api support for finding the relationship of a process definition to an actor or to pooledActors ----------------------------------------------------------------------------------------------- Key: JBPM-952 URL: http://jira.jboss.com/jira/browse/JBPM-952 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.1.4 Environment: jbpm-3.1.4.zip jboss-4.0.5.GA postgresql openSUSE 10.2 Reporter: y o Assigned To: Tom Baeyens Typical use case can be e.g. checking if a user is allowed to start a particular process. Currently this can only be done through manually parsing the actorIdExpression or pooledActorsExpression. http://www.jboss.com/index.html?module=bb&op=viewtopic&t=105021 http://www.jboss.com/index.html?module=bb&op=viewtopic&t=106313 -- 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

19 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-950) jBPM with hibernate2

by Sachin Bapte (JIRA)

jBPM with hibernate2 -------------------- Key: JBPM-950 URL: http://jira.jboss.com/jira/browse/JBPM-950 Project: JBoss jBPM Issue Type: Release Environment: JBoss 4.0.0, jdk1.5.0_05 Reporter: Sachin Bapte Assigned To: Tom Baeyens Hi All, We use JBoss version 4.0.0 as application server which is hibernate2 compatible. I am unable to find a jBPM version which uses hibernate2 to connect to the database, all the jBPM versions use hibernate3. We dont want to change the JBoss Version. Can anyone help me in getting the jBPM with hibernate2 to connect the database. Thanks in advance. Thanks & Regards, Sachin -- 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

19 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-947) timer repeat='true' not repeating from within EAR

by Britt Miner (JIRA)

timer repeat='true' not repeating from within EAR ------------------------------------------------- Key: JBPM-947 URL: http://jira.jboss.com/jira/browse/JBPM-947 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Britt Miner Assigned To: Tom Baeyens Timer repeat='true' doesn't repeat under the jbpm-enterprise.ear that is bundled with jbpm-jpdl-3.2.GA, but it does repeat under the jbpm-console.war that is not part of the EAR. Example process definition: <?xml version="1.0" encoding="UTF-8"?> <process-definition name="Simple Timer Test"> <start-state name='START' > <transition name='done' to='NODE1'/> </start-state> <state name='NODE1'> <event type='node-enter' > <create-timer name='timeout' duedate='30 seconds' repeat='yes' > <script>System.out.println("I reset my timer!");</script> </create-timer> </event> <event type='node-leave' > <cancel-timer name='timeout' /> </event> <transition name='done' to='END'/> </state> <end-state name="END" /> </process-definition> Logging output under jbpm-enterpise.ear: 09:57:30,394 DEBUG [TimerServiceBean] ejb timer [id=1,target=[target=jboss.j2ee:jndiName=local/TimerServiceBean@2104685,service=EJB],remaining=-9,periode=0,in_timeout] fires 09:57:30,396 DEBUG [CommandServiceBean] getting jbpm configuration resource from the environment properties 09:57:30,397 DEBUG [CommandServiceBean] couldn't find configuration property JbpmCfgResource through JNDI 09:57:30,397 DEBUG [CommandServiceBean] getting default jbpm configuration resource (jbpm.cfg.xml) 09:57:30,399 DEBUG [CommandServiceBean] handing over the command execution to the command service 09:57:30,400 DEBUG [JbpmContextInfo] creating jbpm context with service factories '[tx, message, scheduler, logging, persistence, authentication]' 09:57:30,400 DEBUG [JbpmContext] creating org.jbpm.JbpmContext@f42d53 09:57:30,400 DEBUG [CommandServiceBean] executing org.jbpm.scheduler.ejbtimer.ExecuteTimerCommand@cbb612 09:57:30,400 DEBUG [DbPersistenceService] beginning hibernate transaction 09:57:30,526 DEBUG [ExecuteTimerCommand] executing timer 1 09:57:30,618 DEBUG [Timer] executing timer 'timer(timeout,09:57:30,385)' 09:57:30,730 DEBUG [Script] script input: {taskInstance=null, node=State(NODE1), token=Token(/), task=null, executionContext=ExecutionContext[Token(/)]} 09:57:30,744 INFO [STDOUT] I reset my timer! 09:57:30,744 DEBUG [Script] script output: {} 09:57:30,745 DEBUG [Timer] updated timer for repetition 'timer(timeout,09:58:00,385)' in '29640' millis 09:57:30,745 DEBUG [JbpmContext] closing JbpmContext 09:57:30,745 DEBUG [Services] closing service 'persistence': org.jbpm.persistence.jta.JtaDbPersistenceService@f61f5c 09:57:30,745 DEBUG [DbPersistenceService] committing hibernate transaction 09:57:30,745 DEBUG [Services] closing service 'tx': org.jbpm.tx.TxService@84e3f9 After this, the timer is never re-executed. -- 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

19 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1336) Italian patch for jboss portal

by Luca Stancapiano (JIRA)

Italian patch for jboss portal ------------------------------ Key: JBPORTAL-1336 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1336 Project: JBoss Portal Issue Type: Patch Security Level: Public (Everyone can see) Components: Portal CMS, Portal Core, Portal Migration, Portal Portlet, Portal Samples, Portal Search Affects Versions: 2.6.Beta1 Environment: all Reporter: Luca Stancapiano Assigned To: Sohil Shah Fix For: 2.6 Final hi....I send you the patch to translate jboss portal in italian language....Version that I referred is the last current in the svn repository exactly in this path: http://anonsvn.jboss.org/repos/portal/trunk ....bye -- 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

19 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-713) Make Dialects Pluggeable

by Mark Proctor (JIRA)

Make Dialects Pluggeable ------------------------ Key: JBRULES-713 URL: http://jira.jboss.com/jira/browse/JBRULES-713 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m2 -- 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

19 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-895) Better Properties Support

by Mark Proctor (JIRA)

Better Properties Support ------------------------- Key: JBRULES-895 URL: http://jira.jboss.com/jira/browse/JBRULES-895 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.0.MR3 Currently properties are only assignment by the system properties method, we need a cascading system with auto discovery. -- 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-445) behavior of globals?

by G￡bor Lipt￡k (JIRA)

behavior of globals? -------------------- Key: JBRULES-445 URL: http://jira.jboss.com/jira/browse/JBRULES-445 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 3.0.4 Reporter: G￡bor Lipt￡k Assigned To: Mark Proctor Priority: Minor It seems that the value of DRL globals without external env backup is removed between rules: package globaltest import Policy; global java.lang.String text; rule "Foo" salience 999 when Policy() then text="foo"; System.out.println("foo+"+text); end rule "Bar" salience 998 when Policy() then System.out.println("bar+"+text); text="bar"; System.out.println("bar+"+text); end results in: foo+foo bar+null bar+bar The documentation does not seem to provide details if this is the expected behavior. Please comment. Thanks -- 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

19 years, 2 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2007