November 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-987) display non GMT+0 time zones

by Alejandro Guizar (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-987?page=com.atlassian.jira.plugi... ] Alejandro Guizar resolved JBPM-987. ----------------------------------- Resolution: Duplicate Issue Assignee: Alejandro Guizar See issue links for details. > display non GMT+0 time zones > ---------------------------- > > Key: JBPM-987 > URL: https://jira.jboss.org/jira/browse/JBPM-987 > Project: JBoss jBPM > Issue Type: Bug > Components: Console > Affects Versions: jBPM 3.2.0, jBPM 3.2.1 > Reporter: Jean-Louis Rastapoc > Assignee: Alejandro Guizar > Fix For: jBPM 3.3.2 GA > > > The web-console currently uses the default JSF timezone conversion and displays GMT+0. > Other time zones should be read from the client or be configurable. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1888) Allow unlocking Token without knowing the lock owner

by Bernd Ruecker (JIRA)

Allow unlocking Token without knowing the lock owner ---------------------------------------------------- Key: JBPM-1888 URL: https://jira.jboss.org/jira/browse/JBPM-1888 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.0 GA, jBPM 3.3.0 CR1, jBPM 3.2.3, jBPM 3.2.2, jBPM 3.2.1, jBPM 3.2.0 Reporter: Bernd Ruecker Currently the API of the Token is a bit too restrictive: I can lock a token (with a lock owner) and unlock a token (if I know the lock owner). And I can query IF the token is locked (but not by whom). So I would vote for either a method "forceUnlock()" or at least the possibility to "getLockOwner()". -- 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

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Commented: (JBPM-1015) ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB

by Bernd Ruecker (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1015?page=com.atlassian.jira.plug... ] Bernd Ruecker commented on JBPM-1015: ------------------------------------- Okay, I added an addAutoSave to the methods... Tests are all green and my local test with the BAM stuff works fine now :-) So this small change will be released with jbpm 3.3.1 > ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB > -------------------------------------------------------------------------------------------------------------- > > Key: JBPM-1015 > URL: https://jira.jboss.org/jira/browse/JBPM-1015 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.2.1 > Environment: Tomcat 5.0.28 or Jboss > Reporter: Gil Messerman > Assignee: Tom Baeyens > Priority: Critical > Fix For: jBPM 3.2.2 > > > It seems to be a problem with Timer implementation. When some change in process occurs (such as transition or action call), the process instance should be added to jbpmContext to the list of auto saved process instances (actual saving occurs when JBPMContex.close() is called). Apparently Timer.execute does not do it and as a result, the log of all operations performed by Timer.execute is not stored in DB and getting lost. > To fix the problem, the token.getProcessInstance() should be added to "autoSaveProcessInstances" list in JBPMContext. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1015) ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB

by Bernd Ruecker (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1015?page=com.atlassian.jira.plug... ] Bernd Ruecker commented on JBPM-1015: ------------------------------------- There is one problem remaining with this implementation, at least for me at the moment: jbpmContext.save() is called AFTER token.signal(). So if there is an Exception during execution, the jbpmContext.save is never called. Unfortunately I use the LoggingService at the moment to create BAM events (also see http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191842 for some information on that). So in case of exception my own LoggingServices is never called, which is bad! I will add an jbpmContext.loadTokenForUpdate(token) at the mentioned places at the very beginning to add the autoSave we have at the other places of jbpm. And because of the Hibernate Session cache it shouldn't have any negative effects... Then it is consistent overall jbpm. Votes against that? > ProcessLogs that represent changes of process intance that take place within Timer.Execute are not saved in DB > -------------------------------------------------------------------------------------------------------------- > > Key: JBPM-1015 > URL: https://jira.jboss.org/jira/browse/JBPM-1015 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.2.1 > Environment: Tomcat 5.0.28 or Jboss > Reporter: Gil Messerman > Assignee: Tom Baeyens > Priority: Critical > Fix For: jBPM 3.2.2 > > > It seems to be a problem with Timer implementation. When some change in process occurs (such as transition or action call), the process instance should be added to jbpmContext to the list of auto saved process instances (actual saving occurs when JBPMContex.close() is called). Apparently Timer.execute does not do it and as a result, the log of all operations performed by Timer.execute is not stored in DB and getting lost. > To fix the problem, the token.getProcessInstance() should be added to "autoSaveProcessInstances" list in JBPMContext. -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1128) merge processdefinition.xml and gpd.xml in one file

by Ronald van Kuijk (JIRA)

merge processdefinition.xml and gpd.xml in one file --------------------------------------------------- Key: JBPM-1128 URL: http://jira.jboss.com/jira/browse/JBPM-1128 Project: JBoss jBPM Issue Type: Feature Request Affects Versions: jBPM jPDL 3.2.2 Environment: All Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Priority: Minor Currently there is a processdefinition.xml file and a gpd.xml file. Some discussion has taken place on merging them, see forum. -- 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

16 years, 1 month

2
3
0 / 0

[JBoss JIRA] Resolved: (JBPM-719) Create ws dir, resources, build.xml under the project root

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-719?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-719. --------------------------------- Resolution: Out of Date > Create ws dir, resources, build.xml under the project root > ---------------------------------------------------------- > > Key: JBPM-719 > URL: https://jira.jboss.org/jira/browse/JBPM-719 > Project: JBoss jBPM > Issue Type: Feature Request > Environment: n/a > Reporter: Ronald van Kuijk > Priority: Minor > Original Estimate: 2 hours > Time Spent: 2 days, 4 hours > Remaining Estimate: 2 hours > > Create <jbpm.home>/ws and all relevant subdirs according to what already exists (take console as an example) > Create a build.xml file according to what already exists (take console as an example) > Initially add jbossws from <jboss.home> if set, see other issue for getting jbossws in the repository -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-721) create ws call startProcess(String name)

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-721?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-721. --------------------------------- Resolution: Out of Date Needs to be looked at in terms of API functionality > create ws call startProcess(String name) > ----------------------------------------- > > Key: JBPM-721 > URL: https://jira.jboss.org/jira/browse/JBPM-721 > Project: JBoss jBPM > Issue Type: Sub-task > Reporter: Ronald van Kuijk > Priority: Minor > -- 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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-720) create a schema for the jbpm ws frontend

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-720?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-720. --------------------------------- Resolution: Out of Date Needs to be looked at in terms of API functionality > create a schema for the jbpm ws frontend > ---------------------------------------- > > Key: JBPM-720 > URL: https://jira.jboss.org/jira/browse/JBPM-720 > Project: JBoss jBPM > Issue Type: Sub-task > Environment: n/a > Reporter: Ronald van Kuijk > Priority: Minor > Original Estimate: 1 day > Remaining Estimate: 1 day > > It should work with jboss ws 1.0.2.GA (or all since 1.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

16 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1108) create ws interface for retrieving data stored in the jBPM logs

by Vitaliy Kotov (JIRA)

create ws interface for retrieving data stored in the jBPM logs --------------------------------------------------------------- Key: JBPM-1108 URL: http://jira.jboss.com/jira/browse/JBPM-1108 Project: JBoss jBPM Issue Type: Sub-task Reporter: Vitaliy Kotov 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

16 years, 1 month

4
7
0 / 0

[JBoss JIRA] Resolved: (JBPM-718) Add a webservice frontend to jBPM

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-718?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-718. --------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Out of Date Needs to be looked at in terms of API functionality > Add a webservice frontend to jBPM > --------------------------------- > > Key: JBPM-718 > URL: https://jira.jboss.org/jira/browse/JBPM-718 > Project: JBoss jBPM > Issue Type: Feature Request > Environment: n/a > Reporter: Ronald van Kuijk > Priority: Minor > > A webservice frontend is an interesting feature. A schema has to be designed, ws toolkit choosen (jbossws 1.0.2GA?) subdir created in the build, ant files etc... etc...etc... > Subtasks will be created for this. Anyone to jump in, feel free -- 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

16 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues November 2008