June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-709) Update the CVS instructions so people use the correct repository.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-709?page=all ] Thomas Diesler resolved JBPM-709. --------------------------------- Resolution: Out of Date > Update the CVS instructions so people use the correct repository. > ----------------------------------------------------------------- > > Key: JBPM-709 > URL: http://jira.jboss.com/jira/browse/JBPM-709 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Documentation > Reporter: Darran Lofthouse > Assigned To: Tom Baeyens > > Update the CVS instructions so people use the correct repository. > http://sourceforge.net/cvs/?group_id=70542 -- 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-686) externalize a TimeService for obtaining the currentTime

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-686?page=all ] Thomas Diesler resolved JBPM-686. --------------------------------- Resolution: Out of Date > externalize a TimeService for obtaining the currentTime > ------------------------------------------------------- > > Key: JBPM-686 > URL: http://jira.jboss.com/jira/browse/JBPM-686 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Critical > > Now, the new Date() is used to obtain the time. This should be externalized to support simulation in which case the environment can pretend a different time. -- 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-679) Add support for specifying process context variable values in the process definition xml

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-679?page=all ] Thomas Diesler resolved JBPM-679. --------------------------------- Resolution: Out of Date > Add support for specifying process context variable values in the process definition xml > ---------------------------------------------------------------------------------------- > > Key: JBPM-679 > URL: http://jira.jboss.com/jira/browse/JBPM-679 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1.1 > Reporter: Charles Crouch > Assigned To: Tom Baeyens > Priority: Minor > > See forum posting for a full description. Basically it would be handy to be to do something like: > <process-definition name='super'> > <process-state name='p'> > <mycontextvariable>myvalue</mycontextvariable> > <sub-process name='sub' /> > <transition to='q' /> > </process-state> > <process-state name='q'> > <mycontextvariable>myvalue2</mycontextvariable> > <sub-process name='sub' /> > </process-state> > </process-definition> > and > <process-definition name='sub'> > ... > <action class='org.jbpm.tutorial.action.MyActionHandler'/> > ... > </process-definition> > and then have MyActionHandler in the sub process do: > Object object = executionContext.getContextInstance().getVariable("mycontextvariable"); > and have it pick up either myvalue or myvalue2 depending on which part of the process it was being called from -- 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-680) TaskTimerExecutionDbTest - proper jbpmConfiguration is not passed to SchedulerThread

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-680?page=all ] Thomas Diesler resolved JBPM-680. --------------------------------- Resolution: Out of Date > TaskTimerExecutionDbTest - proper jbpmConfiguration is not passed to SchedulerThread > ------------------------------------------------------------------------------------ > > Key: JBPM-680 > URL: http://jira.jboss.com/jira/browse/JBPM-680 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM 3.1.1 > Environment: WebSphere v5.1 Test Environment under WSAD 5.1.2 > DB2 v7 and MySql > Windows XP > Java 1.4.2_06 > Reporter: Chris OBrien > Assigned To: Tom Baeyens > Priority: Critical > > In the test - TaskTimerExecutionDbTest .testTimerExecution > throws: junit.framework.AssertionFailedError: expected:<1> but was:<0> > In the test - TaskTimerExecutionDbTest.testTimerExecutionRepeat > throws: org.jbpm.JbpmException: closed JbpmContext more then once... check your try-finally's around JbpmContexts blocks > I am using a custom jbpmConfiguration (changed my jbpm.test.cfg.xml to reference a db2.hibernate.cfg.xml instead of the default), but it does not get passed to the SchedulerThread. > Creating a new SchedulerThread with the default constructor ends up using the default configuration/context. This causes the test to fail, as it is querying the wrong database inside the SchedulerThread when it looks for all due timers. > Changing lines 146 and 185 from: > new SchedulerThread().executeTimers(); > to: > new SchedulerThread( jbpmConfiguration ).executeTimers(); > ...fixes both the tests from failing. -- 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-612) 10 minute tutorial

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-612?page=all ] Thomas Diesler resolved JBPM-612. --------------------------------- Resolution: Out of Date > 10 minute tutorial > ------------------ > > Key: JBPM-612 > URL: http://jira.jboss.com/jira/browse/JBPM-612 > Project: JBoss jBPM > Issue Type: Task > Components: Documentation > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > A tutorial that explains what jPDL/jBPM can do to experienced developers. > It should NOT contain handholding instructions like 'click here, now you see a this form...' > It should contain the inputs, outputs and important artifacts of using jBPM and explain why using jBPM/jPDL is easier for them then writing it themselves. > It should be an example that builds up in 3 stages: > 1) a 3-task simple straight through process > 2) add an email notification and reminder > 3) include a piece of custom code via an action > The first stage should highlight the 2 goals of jBPM/jPDL: > * it's a language that can specify an execution spanning wait states (long running) > * the graphical view of the process is the common language between developers and business analysts. it should be stressed that this view is a projection of the process (no round trip engineering). -- 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-640) Include use of scripts in training

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-640?page=all ] Thomas Diesler resolved JBPM-640. --------------------------------- Resolution: Out of Date > Include use of scripts in training > ---------------------------------- > > Key: JBPM-640 > URL: http://jira.jboss.com/jira/browse/JBPM-640 > Project: JBoss jBPM > Issue Type: Task > Components: Training > Reporter: Koen Aers > Assigned To: Koen Aers > -- 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-656) tutorial examples

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-656?page=all ] Thomas Diesler resolved JBPM-656. --------------------------------- Resolution: Out of Date > tutorial examples > ----------------- > > Key: JBPM-656 > URL: http://jira.jboss.com/jira/browse/JBPM-656 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine, Documentation > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > The tutorial examples should be revised and become the main source of simple getting started introductions. > This is to be done on the HEAD of cvs, in module jbpm.3, directory jpdl/examples. See http://wiki.jboss.org/wiki/Wiki.jsp?page=JbpmBuildingTheSources on getting started with jBPM sources. -- 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-648) auto schema creation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-648?page=all ] Thomas Diesler resolved JBPM-648. --------------------------------- Resolution: Out of Date > auto schema creation > -------------------- > > Key: JBPM-648 > URL: http://jira.jboss.com/jira/browse/JBPM-648 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > * Check out portal: core/src/main/org.jboss.portal.core.hibernate.SessionFactoryBinder : that is a nice mechanism of determining wether the schema needs an update, a create or is up to 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-650) Describe usage of actionhandlers in separate jar files

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-650?page=all ] Thomas Diesler resolved JBPM-650. --------------------------------- Resolution: Out of Date > Describe usage of actionhandlers in separate jar files > ------------------------------------------------------ > > Key: JBPM-650 > URL: http://jira.jboss.com/jira/browse/JBPM-650 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Documentation > Environment: N/A > Reporter: Ronald van Kuijk > Assigned To: Tom Baeyens > Priority: Trivial > > There is some unclearity about the usage of actionhandlers in separate jar files. They do not seem to work either in the editor nor in the runtime enviroment. It would help to describe the options in a little detail. The question is at least addressed in the post referenced below. I'll try to find some more questions in this directon and post the links here -- 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-632) DelegationException serialization broken

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-632?page=all ] Thomas Diesler resolved JBPM-632. --------------------------------- Resolution: Out of Date > DelegationException serialization broken > ---------------------------------------- > > Key: JBPM-632 > URL: http://jira.jboss.com/jira/browse/JBPM-632 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1 > Environment: Used in JBoss 3.2.7 on Windows XP, JDK 1.4.1 > Reporter: Reid Pinchback > Assigned To: Tom Baeyens > Priority: Minor > > Throwables are java.io.Serializable. DelegationException is a throwable and hence serializable. > It contains a non-transient reference to non-serializable data (ExecutionContext). If an Action > throws a perfectly serializable RuntimeException it gets wrapped in a non-serializable DelegationException > and results in unmarshalling errors when propagated to an EJB client. -- 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