January 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1120) Overwriting resource-need not yet implemented

by Bernd Ruecker (JIRA)

Overwriting resource-need not yet implemented --------------------------------------------- Key: JBPM-1120 URL: http://jira.jboss.com/jira/browse/JBPM-1120 Project: JBoss jBPM Issue Type: Feature Request Components: Simulation Reporter: Bernd Ruecker Assigned To: Tom Baeyens Priority: Minor This configudration in the exmperiment.xml should work but is not yet implemented: <task-overwrite task-name='processing with machine' time-distribution='...'> <resource-needed pool='big machine' amount='2' /> </task-overwrite> -- 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1124) Simulation doesn't support sub-process, super-state and timer

by Bernd Ruecker (JIRA)

Simulation doesn't support sub-process, super-state and timer ------------------------------------------------------------- Key: JBPM-1124 URL: http://jira.jboss.com/jira/browse/JBPM-1124 Project: JBoss jBPM Issue Type: Feature Request Components: Simulation Reporter: Bernd Ruecker Assigned To: Tom Baeyens Priority: Minor As the summary says, these concepts are not yet supported. -- 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1194) Enable variable reference evaluation in Mail Templates

by Matthias Grossmann (JIRA)

Enable variable reference evaluation in Mail Templates ------------------------------------------------------ Key: JBPM-1194 URL: http://jira.jboss.com/jira/browse/JBPM-1194 Project: JBoss jBPM Issue Type: Patch Components: Core Engine Affects Versions: jBPM jPDL 3.2 Reporter: Matthias Grossmann Assigned To: Tom Baeyens Changes in org.jbpm.mail.Mail: public String getSubject() { if (subject==null) return null; Object parsedValue = null; String ret = subject; do { ret = evaluate(ret); ret = JbpmExpressionEvaluator.translateExpressionToDollars(ret); parsedValue = new ExpressionEvaluatorImpl().parseExpressionString(ret); } while (!(parsedValue instanceof String)); return ret; } public String getText() { if (text==null) return null; Object parsedValue = null; String ret = text; do { ret = evaluate(ret); ret = JbpmExpressionEvaluator.translateExpressionToDollars(ret); parsedValue = new ExpressionEvaluatorImpl().parseExpressionString(ret); } while (!(parsedValue instanceof String)); return ret; } -- 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

17 years, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1454) Add some random when JobExecutorThread acquiring job

by Pavel Kadlec (JIRA)

Add some random when JobExecutorThread acquiring job ----------------------------------------------------- Key: JBPM-1454 URL: https://jira.jboss.org/jira/browse/JBPM-1454 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Pavel Kadlec -- 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBPM-1770) Using the same entityManager for Seam and jbpm

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1770?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1770. ---------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Won't Fix Future jBPM3 releases can only contain bug fixes. All effort goes into jBPM4. > Using the same entityManager for Seam and jbpm > ---------------------------------------------- > > Key: JBPM-1770 > URL: https://jira.jboss.org/jira/browse/JBPM-1770 > Project: JBoss jBPM > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Console > Reporter: stefan meyer > > I wrote an entry in the forum and was asked to create a JIRA issue. Following is the forum entry and my code. The code is ugly whenever calls come via MDBs. ManagedPersistenceContext.beforeCompletion does not work nicely with this implementation. Because I cannot get the entityManager anymore. Even if the code was called in destroy the entitymanager would be gone. If ManagedJbpmContext was in conversation scope and depended on ManagedPersistenceContext and the dependency would lead to the destruction of managedJbpmContext first, then things would be better. > The problem is actually only that Jbpm-DbLogging does not work. Maybe that should be fixed. Or Maybe the Jbpm people should work on it. > " > Jbpm and seam using the same entityManager makes sense, because storing entities in variable context and refernecing processInstance or token from entities is possible. > I have the following problem though. My SeamPersistenceService Implementation of Jbpm's PersistenceService is closed with the destruction of the ManagedJbpmContext. Since ManagedJbpmContext is in scope EVENT and entityManager in scope CONVERSATION the entityManager is destroyed before. Jbpm tries to save the log entities upon close and thus fails because the seam managed entityManager is gone and even closed. > In my scenario it would help to close JbpmContext in the destroy Method of managedJbpmContext. Transactions and Connections are managed by JbpmContext anyways. Unfortunately direct access to the entityManager will not be possiblle in destroy because the entityManager is removed from Contexts before the ManagedJbpmContext. Maybe ManagedJbpmContext should also be in the Conversation scope. > Could you include an alternative version of ManagedJbpmContext that works with a SeamPersistenceService? > " > Here is my Implementation of Jbpm's PersistenceService that uses a seam managed EntityManager (actually the wrapped hibernate session): > package xx.jbpm.persistence.seam; > import org.apache.commons.logging.Log; > import org.apache.commons.logging.LogFactory; > import org.hibernate.Session; > import org.jboss.seam.Component; > import org.jboss.seam.ScopeType; > import org.jboss.seam.contexts.Contexts; > import org.jbpm.persistence.db.DbPersistenceServiceFactory; > import org.jbpm.persistence.jta.JtaDbPersistenceService; > public class SeamPersistenceService extends JtaDbPersistenceService > { > private static Log log = LogFactory.getLog(SeamPersistenceService.class); > public SeamPersistenceService(final DbPersistenceServiceFactory persistenceServiceFactory) > { > super(persistenceServiceFactory); > } > @Override > public void close() > { > // session is not closed here. > super.close(); > } > @Override > public Session getSession() > { > boolean initialized = Contexts.isApplicationContextActive(); > if (initialized) > { > Session hibernateSession = (Session) Component.getInstance("hibernateSession", ScopeType.EVENT); > if (hibernateSession == null || !hibernateSession.isOpen()) > { > // see comment in else clause > return new DummySession(); > } > else > { > return hibernateSession; > } > > } > else > { > // seam is not active any more but entityManager is closed in transaction synchronization. > // unfortunately ManagedJbpmContext wants to flush the entityManager in beforeCompletion, but we can't get > // it via seam anymore. This is probably happening right now. Also saving of instances might happen here. These > // are all persistent entites - that is why seam ignores it. Except for the log entries - those get lost > // when db logging is used. return Dummy Session > return new DummySession(); > } > } > } > Extract from DummySession: > ... > public Serializable save(final Object object) throws HibernateException > { > try > { > Method getIdMethod = object.getClass().getMethod("getId", new Class[0]); > Object value = getIdMethod.invoke(object, new Object[0]); > if (value != null && ((Number) value).intValue() == 0) > { > Logger.getLogger("dummy session").warn("not saving transient entity " + object.getClass().getName()); > } > } > catch (Exception e) > { > Logger.getLogger("dummy session").warn("cannot check state of entities " + object.getClass().getName(), e); > } > return null; > } > ... -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1773) introduce task-cancel event when cancelling a task instead of a task-end event

by Ronald van Kuijk (JIRA)

introduce task-cancel event when cancelling a task instead of a task-end event ------------------------------------------------------------------------------- Key: JBPM-1773 URL: https://jira.jboss.org/jira/browse/JBPM-1773 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.0 CR1, jBPM 3.2.3, SOA 4.2 CP02 Environment: N/A Reporter: Ronald van Kuijk Priority: Minor Fix For: jBPM 3.3.1 GA When cancelling a task, a task-end event is generated. This should in fact be a task-cancel event since they are different. Small patch and running the tests shows that no tests fail when this change is made. -- 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

17 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-1705) jBPM3 implementation of the API

by Thomas Diesler (JIRA)

jBPM3 implementation of the API ------------------------------- Key: JBPM-1705 URL: https://jira.jboss.org/jira/browse/JBPM-1705 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Thomas Diesler -- 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

17 years, 3 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBPM-831) avoid using default id generator

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-831?page=com.atlassian.jira.plugi... ] Thomas Diesler resolved JBPM-831. --------------------------------- Resolution: Rejected Future jBPM3 releases can only contain bug fixes. All effort goes into jBPM4. > avoid using default id generator > -------------------------------- > > Key: JBPM-831 > URL: https://jira.jboss.org/jira/browse/JBPM-831 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1.2 > Environment: The problem is common to all platform. > Issue is identifed on Oracle 9.1 specifically. > Reporter: Wenbo Zhu > > The Id generator should be named explicitly, which is currently not. > <id name="id" column="ID_"><generator class="native" /></id> > This will introdcue issue when jbpm schema has to be updated (dropped, e.g.) as the db may be shared with other apps that uses default hibernate id generator too .. in case of Oracle, it's "hibernate_sequence". > - Wenbo -- 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

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1149) UI Version Requirement added to Task

by Britt Miner (JIRA)

UI Version Requirement added to Task ------------------------------------ Key: JBPM-1149 URL: http://jira.jboss.com/jira/browse/JBPM-1149 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Britt Miner Assigned To: Tom Baeyens Addition of a "ui=" attribute to the jPDL Task element and entity. -- 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

17 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1150) UI Version Requirement added to ProcessDef

by Britt Miner (JIRA)

UI Version Requirement added to ProcessDef ------------------------------------------ Key: JBPM-1150 URL: http://jira.jboss.com/jira/browse/JBPM-1150 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Reporter: Britt Miner Assigned To: Tom Baeyens Addition of a "ui=" attribute to the jPDL process-definition element and ProcessDefinition entity. -- 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

17 years, 3 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2009