June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-425) Session Factory is in a static variable in the ScheduleThread class

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-425?page=all ] Thomas Diesler resolved JBPM-425. --------------------------------- Resolution: Out of Date > Session Factory is in a static variable in the ScheduleThread class > ------------------------------------------------------------------- > > Key: JBPM-425 > URL: http://jira.jboss.com/jira/browse/JBPM-425 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Environment: All > Reporter: Adam Schwabacher > Assigned To: Tom Baeyens > > Our applications needs the ability of running in multiple environments. We do this by passing the Hibernate configuration in at runtime. We also need the abiltiy of shutting down all factories and releasing all resources. I know shutting down the Application Server would do this, but for some of our applications this is not a reasonable request. > The problem with the ScheduleThread class is that since the JbpmSessionFactory is a static variable it cannot be unloaded by the VM. I can close all session factories, but since this is a static variable, the factoryt cannot be effectively reloaded. This causes a problem with the database connections. > I close the JbpmSessionFactory, but on subsequent launches of this class I cannot access the database because of 'Generic' connection exceptions. I verified that with the abiltiy of dynamically supplying a JbpmSessionFactory at runtime this problem does not exists. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-443) JPBM does not work with MySQL 5.0

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-443?page=all ] Thomas Diesler resolved JBPM-443. --------------------------------- Resolution: Out of Date > JPBM does not work with MySQL 5.0 > --------------------------------- > > Key: JBPM-443 > URL: http://jira.jboss.com/jira/browse/JBPM-443 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0, jBPM 3.1, jBPM 3.0.1, jBPM 3.0.2, jBPM 3.0.3, jBPM jPDL 3.2 alpha 1, jBPM 3.1.1, jBPM 3.1.2, jBPM 3.0.4 > Environment: Windows XP, Mysql 5.0 beta2, JBPM 3.0 > Reporter: Ravi Prakash Reddy Ummadi > Assigned To: Tom Baeyens > > When JBPM is used with MySQL 5.0, the process is skipping the intermediate steps in the process definition. > The behaviour is unpredictable. The same works fine with MySQL 4.1 and other databases. > The problem may be in DB scripts ( DB scrips run fine though) or .hbm.xml files . -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-418) action in ActionHandler is null in a timer

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-418?page=all ] Thomas Diesler resolved JBPM-418. --------------------------------- Resolution: Out of Date > action in ActionHandler is null in a timer > ------------------------------------------ > > Key: JBPM-418 > URL: http://jira.jboss.com/jira/browse/JBPM-418 > Project: JBoss jBPM > Issue Type: Feature Request > Reporter: Leandro Scasso > Assigned To: Tom Baeyens > Priority: Minor > > when a timer expires and the timer has actions, the action in the executeContext in the ActionHandler is null. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-411) Interface for GraphSession, ContextSession and so on

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-411?page=all ] Thomas Diesler resolved JBPM-411. --------------------------------- Resolution: Out of Date > Interface for GraphSession, ContextSession and so on > ---------------------------------------------------- > > Key: JBPM-411 > URL: http://jira.jboss.com/jira/browse/JBPM-411 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Thijs Terlouw > Assigned To: Tom Baeyens > Priority: Optional > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > I am introducing security into my webapplication by using the Proxy pattern. For this purpose I made a "SecureJbpmSessionInterceptor extends JbpmSessionInterceptor implements ContextInterceptor" that does basically the same as the JbpmSessionInterceptor, but now provides security by wrapping the Sessions into a Proxy. > Example: > [SecureJbpmSessionInterceptor] > IGraphSession graphSession = jbpmSession.getGraphSession(); > IGraphSession secureGraphSession = (IGraphSession) AuthorizationHandler.newInstance(graphSession); > ThreadContext.put(taskMgmtSessionKey, secureTaskMgmtSession); //secure version ! > Where AuthorizationHandler implements InvocationHandler > The proxy pattern is very usefull to provide Security I think, but it needs Interfaces to the classes. That's why I introduced Interfaces: > public class GraphSession implements IGraphSession > public class TaskMgmtSession implements ITaskMgmtSession, Serializable > The IGraphSession and ITaskMgmtSession are automatically generated Interfaces (by the IDE). Because of the usage of Interfaces, it is MUCH easier to extend. I would very much like to emphasize that these classes should also implement an Interface. This allows me to put all the security-checks (based on JAAS) into the AuthorizationHandler, and prevents all the other code from becoming more complex. This is a bit like AOP, but only requires a very simple change to the code: > Add some Interfaces in the jbpm.3\src\java.jbpm\org\jbpm\db and make sure that org.jbpm.tc.db.JbpmSessionContext returns the Interfaces like this: > public static IGraphSession getGraphSession() { > return getGraphSession(GraphSession.class.getName()); > } -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-403) converter for storing ejb3 entity beans in process variables

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-403?page=all ] Thomas Diesler resolved JBPM-403. --------------------------------- Resolution: Out of Date > converter for storing ejb3 entity beans in process variables > ------------------------------------------------------------ > > Key: JBPM-403 > URL: http://jira.jboss.com/jira/browse/JBPM-403 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Gavin King > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-405) review usage of jbpm in seam

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-405?page=all ] Thomas Diesler resolved JBPM-405. --------------------------------- Resolution: Out of Date > review usage of jbpm in seam > ---------------------------- > > Key: JBPM-405 > URL: http://jira.jboss.com/jira/browse/JBPM-405 > Project: JBoss jBPM > Issue Type: Task > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > i'll first finish the outstanding features needed for seam. then i'll review the current implementation and update steve on what could be improved and how to use the new features. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-398) PriorityHandler calculation class for TaskInstances

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-398?page=all ] Thomas Diesler resolved JBPM-398. --------------------------------- Resolution: Out of Date > PriorityHandler calculation class for TaskInstances > --------------------------------------------------- > > Key: JBPM-398 > URL: http://jira.jboss.com/jira/browse/JBPM-398 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Britt Miner > Assigned To: Tom Baeyens > > I'd like to see the ability to use a custom class associated with a Task in the process definition to calculate a real time priority number for a taskInstance (like for use in a user's task list.) (I know the priority= attribute is up for fixing :) Maybe this would be the same "priority" or maybe a different property. Perhaps the calculation would only be made when the developer calls a taskInstance.getCalculatedPriority() method. > The use of a custom class on the TaskInstance to calculate the priority value would allow tasks in a queue to be prioritized according to dynamic business factors (ie. age of the process, not just age of the task; number of trouble tickets currently open against a customer; VIP status; etc.) > This type of prioritized view is important for queue and task driven environments where users do all their work off of their queues. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-410) taskInstance.setPooledActors() doesn't set actorID to null

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-410?page=all ] Thomas Diesler resolved JBPM-410. --------------------------------- Resolution: Out of Date > taskInstance.setPooledActors() doesn't set actorID to null > ---------------------------------------------------------- > > Key: JBPM-410 > URL: http://jira.jboss.com/jira/browse/JBPM-410 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 alpha 1, jBPM 3.0, jBPM 3.0 alpha 2, jBPM 3.0 alpha 3, jBPM 3.0 alpha 4, jBPM 3.0 beta 2, jBPM 3.0 beta 3, jBPM 3.0 alpha 5, jBPM 3.0 beta 1, jBPM 3.0 beta 4, jBPM 3.0.1 > Reporter: Thijs Terlouw > Assigned To: Tom Baeyens > Priority: Minor > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > TaskMgmtSession.findPooledTaskInstancesByActorId() requires the TaskInstance.actorId to be set to <null> to be able to retrieve the pooled actors. > [TaskInstance.java] > public void setPooledActors(String[] actorIds) { > this.pooledActors = PooledActor.createPool(actorIds); > } > PROBLEM: > This does not reset the actorId to null, so this has to happen in the client code. > Client code looks like this: > String[] pooledactors; > taskInstance.setActorId(null); > taskInstance.setPooledActors(pooledactors); > SOLUTION: > [TaskInstance.java] > public void setPooledActors(String[] actorIds) { > this.actorId = null; > this.pooledActors = PooledActor.createPool(actorIds); > } -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-406) outstanding issues for seam integration

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-406?page=all ] Thomas Diesler resolved JBPM-406. --------------------------------- Resolution: Out of Date > outstanding issues for seam integration > --------------------------------------- > > Key: JBPM-406 > URL: http://jira.jboss.com/jira/browse/JBPM-406 > Project: JBoss jBPM > Issue Type: Task > 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-394) TaskInstance / Task not set in ExecutionContext when start()-event is fired

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-394?page=all ] Thomas Diesler resolved JBPM-394. --------------------------------- Resolution: Out of Date > TaskInstance / Task not set in ExecutionContext when start()-event is fired > --------------------------------------------------------------------------- > > Key: JBPM-394 > URL: http://jira.jboss.com/jira/browse/JBPM-394 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Environment: jbpm-starters-kit-with-eclipse-3.0 > Reporter: Ingo Burth > Assigned To: Tom Baeyens > > Before firing the start()-event an executionContext-Object is prepared. > But TaskInstance.start() doesn't fill the executionContext's attributes TaskInstance and Task (which is done for TaskInstance.create(..)/TaskInstance.assign(..)); > For more details refer to the forum ref. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2008