June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-594) cancel-timer doesn't work

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-594?page=all ] Thomas Diesler resolved JBPM-594. --------------------------------- Resolution: Out of Date > cancel-timer doesn't work > ------------------------- > > Key: JBPM-594 > URL: http://jira.jboss.com/jira/browse/JBPM-594 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM 3.1 > Environment: windowsXP, jdk1.5.0_06, Jboss 4.0.4RC1 > Reporter: Ramil Israfilov > Assigned To: Tom Baeyens > > I have a process definition which uses timer: > <?xml version="1.0" encoding="UTF-8"?> > <process-definition xmlns="urn:jbpm.org:jpdl-3.1" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="urn:jbpm.org:jpdl-3.1 http://jbpm.org/xsd/jpdl-3.1.xsd" > name="ramtest"> > <start-state name="start"> > <transition name="t1" to="state1"></transition> > </start-state> > <state name="state1"> > <timer duedate="10 seconds" repeat="true" name="aaa"> > <action class="be.certipost.jc.jbpm.actions.testAction"></action> > </timer> > <transition name="tonode1" to="node1"></transition> > <transition name="back" to="state1"></transition> >  > <event type="node-leave"> > <cancel-timer name="aaa"/> > </event> > > </state> > <node name="node1"> > > <script> > <expression>System.out.println("node node1")</expression> > </script> > <transition name="t3" to="end1"></transition> > </node> > <end-state name="end1"> > > </end-state> > </process-definition> > Action in timer is called. It checks some other table and calls token.signal("tonode1") > so process continues on node1 and so on.. But timer remains in table and it is called again. As you can see Idefined an event which should remove timer on node-leave event. But it doesn't. > Here is the exefute method of testAction: > public void execute(ExecutionContext ctx) throws Exception { > log.info("test Action called"); > > boolean flag=checkFlag(ctx); > > if(flag) { > > ctx.getToken().signal("tonode1"); > } > > > } -- 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-561) add configuration for creating the tables automatically

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-561?page=all ] Thomas Diesler resolved JBPM-561. --------------------------------- Resolution: Out of Date > add configuration for creating the tables automatically > ------------------------------------------------------- > > Key: JBPM-561 > URL: http://jira.jboss.com/jira/browse/JBPM-561 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > For portal integration, this is an interesting feature. This would sync between jbpm and portal table creation. -- 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-511) use service directly

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-511?page=all ] Thomas Diesler resolved JBPM-511. --------------------------------- Resolution: Out of Date > use service directly > -------------------- > > Key: JBPM-511 > URL: http://jira.jboss.com/jira/browse/JBPM-511 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Trivial > > services are now used indirectly. meaning that the non-persisted data members in the instances are used to store service operations. during the jbpmContext.save, all this data is interpreted and the services are invoked. > most of those service invocations should be done directly. this implies that a large part of the POJO test suite will have to be revised to accomodate this. probably a common base class will be sufficient. > regards, tom. -- 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-542) integrate jbpm test into the overall jboss test suite

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-542?page=all ] Thomas Diesler resolved JBPM-542. --------------------------------- Resolution: Out of Date > integrate jbpm test into the overall jboss test suite > ----------------------------------------------------- > > Key: JBPM-542 > URL: http://jira.jboss.com/jira/browse/JBPM-542 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > this could include: > * checking wether the JbpmConfiguration is properly deployed > * deploying a process > * webapp tests ? -- 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-509) improve jbpm training material and update 3.1 changes

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-509?page=all ] Thomas Diesler resolved JBPM-509. --------------------------------- Resolution: Out of Date > improve jbpm training material and update 3.1 changes > ----------------------------------------------------- > > Key: JBPM-509 > URL: http://jira.jboss.com/jira/browse/JBPM-509 > Project: JBoss jBPM > Issue Type: Task > Components: Training > Reporter: Tom Baeyens > Assigned To: Koen Aers > Priority: Critical > > the training should be updated to jbpm 3.1 and improved. the previous remarks were that it was too theoretic. also 3.1 has got some significant changes that should be reflected in the training. both of these should be done in one revision of the training. -- 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-520) add automatic check for license headers

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-520?page=all ] Thomas Diesler resolved JBPM-520. --------------------------------- Resolution: Out of Date > add automatic check for license headers > --------------------------------------- > > Key: JBPM-520 > URL: http://jira.jboss.com/jira/browse/JBPM-520 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > 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-549) iSeries incompatibility - statement too long due to many 4000 byte strings in select statement

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-549?page=all ] Thomas Diesler resolved JBPM-549. --------------------------------- Resolution: Out of Date > iSeries incompatibility - statement too long due to many 4000 byte strings in select statement > ---------------------------------------------------------------------------------------------- > > Key: JBPM-549 > URL: http://jira.jboss.com/jira/browse/JBPM-549 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM 3.0.2 > Environment: DB2 for iSeries version 5 release 3, client running on Windows > Reporter: Paul Newport > Assigned To: Tom Baeyens > > Because there are many fields in the JBPM schema of type string, length 4000, when you use hibernate to generate the schema you end up with varchars of length 4000 when running it against DB2 for iSeries. > As soon as you run queries such as that posted at the bottom you get this: > SQL State: 54010 > Vendor Code: -101 > Message: [SQL0101] SQL statement too long or complex. Cause . . . . . : The SQL statement is longer than the limit allowed for length or complexity. The reason code is 3. The sum of the lengths of the non-LOB columns in a select list, table, view definition, or user defined table function is greater than 32766 or the definition contains a LOB and the sum of the lengths specified on the ALLOCATE clause for varying-length fields and the non-varying field lengths is greater than 32740. The maximum length is reduced if any of the columns are varying-length or allow null values. > A suggested fix is to change the mapping files for properties that have string lengths of "4000" bytes to be "text" rather than "string", as the iSeries jdbc driver will only create clobs when the strign size is over 32k in length. > Another solution would be to revisit string lengths to see if they all really need to be 4000 bytes long. > As it stands I am patching hte hibernate mapping files manually but obviously would prefer not to. > Here is the statement in question: > select definition0_.PROCESSDEFINITION_ as PROCESSD4_22_, definition0_.ID_ as ID1_22_, definition0_.NAME_ as NAME3_22_, definition0_.ID_ as ID1_16_21_, definition0_.NAME_ as NAME3_16_21_, definition0_.PROCESSDEFINITION_ as PROCESSD4_16_21_, definition0_.STARTTASK_ as STARTTASK5_16_21_, definition0_.CLASS_ as CLASS2_16_21_, task1_.ID_ as ID1_14_0_, task1_.NAME_ as NAME2_14_0_, task1_.PROCESSDEFINITION_ as PROCESSD3_14_0_, task1_.DESCRIPTION_ as DESCRIPT4_14_0_, task1_.ISBLOCKING_ as ISBLOCKING5_14_0_, task1_.DUEDATE_ as DUEDATE6_14_0_, task1_.TASKMGMTDEFINITION_ as TASKMGMT7_14_0_, task1_.TASKNODE_ as TASKNODE8_14_0_, task1_.STARTSTATE_ as STARTSTATE9_14_0_, task1_.ASSIGNMENTDELEGATION_ as ASSIGNM10_14_0_, task1_.SWIMLANE_ as SWIMLANE11_14_0_, task1_.TASKCONTROLLER_ as TASKCON12_14_0_, processdef2_.ID_ as ID1_4_1_, processdef2_.NAME_ as NAME2_4_1_, processdef2_.VERSION_ as VERSION3_4_1_, processdef2_.ISTERMINATIONIMPLICIT_ as ISTERMIN4_4_1_, processdef2_.STARTSTATE_ as STARTSTATE5_4_1_, startstate3_.ID_ as ID1_5_2_, startstate3_.NAME_ as NAME3_5_2_, startstate3_.PROCESSDEFINITION_ as PROCESSD4_5_2_, startstate3_.ACTION_ as ACTION5_5_2_, startstate3_.SUPERSTATE_ as SUPERSTATE6_5_2_, processdef4_.ID_ as ID1_4_3_, processdef4_.NAME_ as NAME2_4_3_, processdef4_.VERSION_ as VERSION3_4_3_, processdef4_.ISTERMINATIONIMPLICIT_ as ISTERMIN4_4_3_, processdef4_.STARTSTATE_ as STARTSTATE5_4_3_, action5_.ID_ as ID1_8_4_, action5_.NAME_ as NAME3_8_4_, action5_.ISPROPAGATIONALLOWED_ as ISPROPAG4_8_4_, action5_.REFERENCEDACTION_ as REFERENC5_8_4_, action5_.ACTIONDELEGATION_ as ACTIONDE6_8_4_, action5_.EVENT_ as EVENT7_8_4_, action5_.PROCESSDEFINITION_ as PROCESSD8_8_4_, action5_.EXPRESSION_ as EXPRESSION9_8_4_, action5_.TIMERNAME_ as TIMERNAME10_8_4_, action5_.DUEDATE_ as DUEDATE11_8_4_, action5_.REPEAT_ as REPEAT12_8_4_, action5_.TRANSITIONNAME_ as TRANSIT13_8_4_, action5_.TIMERACTION_ as TIMERAC14_8_4_, action5_.class as class8_4_, action6_.ID_ as ID1_8_5_, action6_.NAME_ as NAME3_8_5_, action6_.ISPROPAGATIONALLOWED_ as ISPROPAG4_8_5_, action6_.REFERENCEDACTION_ as REFERENC5_8_5_, action6_.ACTIONDELEGATION_ as ACTIONDE6_8_5_, action6_.EVENT_ as EVENT7_8_5_, action6_.PROCESSDEFINITION_ as PROCESSD8_8_5_, action6_.EXPRESSION_ as EXPRESSION9_8_5_, action6_.TIMERNAME_ as TIMERNAME10_8_5_, action6_.DUEDATE_ as DUEDATE11_8_5_, action6_.REPEAT_ as REPEAT12_8_5_, action6_.TRANSITIONNAME_ as TRANSIT13_8_5_, action6_.TIMERACTION_ as TIMERAC14_8_5_, action6_.class as class8_5_, delegation7_.ID_ as ID1_10_6_, delegation7_.CLASSNAME_ as CLASSNAME2_10_6_, delegation7_.CONFIGURATION_ as CONFIGUR3_10_6_, delegation7_.CONFIGTYPE_ as CONFIGTYPE4_10_6_, delegation7_.PROCESSDEFINITION_ as PROCESSD5_10_6_, processdef8_.ID_ as ID1_4_7_, processdef8_.NAME_ as NAME2_4_7_, processdef8_.VERSION_ as VERSION3_4_7_, processdef8_.ISTERMINATIONIMPLICIT_ as ISTERMIN4_4_7_, processdef8_.STARTSTATE_ as STARTSTATE5_4_7_, event9_.ID_ as ID1_7_8_, event9_.EVENTTYPE_ as EVENTTYPE2_7_8_, event9_.TYPE_ as TYPE3_7_8_, event9_.GRAPHELEMENT_ as GRAPHELE4_7_8_, processdef10_.ID_ as ID1_4_9_, processdef10_.NAME_ as NAME2_4_9_, processdef10_.VERSION_ as VERSION3_4_9_, processdef10_.ISTERMINATIONIMPLICIT_ as ISTERMIN4_4_9_, processdef10_.STARTSTATE_ as STARTSTATE5_4_9_, action11_.ID_ as ID1_8_10_, action11_.NAME_ as NAME3_8_10_, action11_.ISPROPAGATIONALLOWED_ as ISPROPAG4_8_10_, action11_.REFERENCEDACTION_ as REFERENC5_8_10_, action11_.ACTIONDELEGATION_ as ACTIONDE6_8_10_, action11_.EVENT_ as EVENT7_8_10_, action11_.PROCESSDEFINITION_ as PROCESSD8_8_10_, action11_.EXPRESSION_ as EXPRESSION9_8_10_, action11_.TIMERNAME_ as TIMERNAME10_8_10_, action11_.DUEDATE_ as DUEDATE11_8_10_, action11_.REPEAT_ as REPEAT12_8_10_, action11_.TRANSITIONNAME_ as TRANSIT13_8_10_, action11_.TIMERACTION_ as TIMERAC14_8_10_, action11_.class as class8_10_, superstate12_.ID_ as ID1_5_11_, superstate12_.NAME_ as NAME3_5_11_, superstate12_.PROCESSDEFINITION_ as PROCESSD4_5_11_, superstate12_.ACTION_ as ACTION5_5_11_, superstate12_.SUPERSTATE_ as SUPERSTATE6_5_11_, taskmgmtde13_.ID_ as ID1_16_12_, taskmgmtde13_.NAME_ as NAME3_16_12_, taskmgmtde13_.PROCESSDEFINITION_ as PROCESSD4_16_12_, taskmgmtde13_.STARTTASK_ as STARTTASK5_16_12_, tasknode14_.ID_ as ID1_5_13_, tasknode14_.NAME_ as NAME3_5_13_, tasknode14_.PROCESSDEFINITION_ as PROCESSD4_5_13_, tasknode14_.ACTION_ as ACTION5_5_13_, tasknode14_.SUPERSTATE_ as SUPERSTATE6_5_13_, tasknode14_.SIGNAL_ as SIGNAL9_5_13_, tasknode14_.CREATETASKS_ as CREATET10_5_13_, startstate15_.ID_ as ID1_5_14_, startstate15_.NAME_ as NAME3_5_14_, startstate15_.PROCESSDEFINITION_ as PROCESSD4_5_14_, startstate15_.ACTION_ as ACTION5_5_14_, startstate15_.SUPERSTATE_ as SUPERSTATE6_5_14_, delegation16_.ID_ as ID1_10_15_, delegation16_.CLASSNAME_ as CLASSNAME2_10_15_, delegation16_.CONFIGURATION_ as CONFIGUR3_10_15_, delegation16_.CONFIGTYPE_ as CONFIGTYPE4_10_15_, delegation16_.PROCESSDEFINITION_ as PROCESSD5_10_15_, swimlane17_.ID_ as ID1_13_16_, swimlane17_.NAME_ as NAME2_13_16_, swimlane17_.ASSIGNMENTDELEGATION_ as ASSIGNME3_13_16_, swimlane17_.TASKMGMTDEFINITION_ as TASKMGMT4_13_16_, delegation18_.ID_ as ID1_10_17_, delegation18_.CLASSNAME_ as CLASSNAME2_10_17_, delegation18_.CONFIGURATION_ as CONFIGUR3_10_17_, delegation18_.CONFIGTYPE_ as CONFIGTYPE4_10_17_, delegation18_.PROCESSDEFINITION_ as PROCESSD5_10_17_, taskmgmtde19_.ID_ as ID1_16_18_, taskmgmtde19_.NAME_ as NAME3_16_18_, taskmgmtde19_.PROCESSDEFINITION_ as PROCESSD4_16_18_, taskmgmtde19_.STARTTASK_ as STARTTASK5_16_18_, taskcontro20_.ID_ as ID1_15_19_, taskcontro20_.TASKCONTROLLERDELEGATION_ as TASKCONT2_15_19_, delegation21_.ID_ as ID1_10_20_, delegation21_.CLASSNAME_ as CLASSNAME2_10_20_, delegation21_.CONFIGURATION_ as CONFIGUR3_10_20_, delegation21_.CONFIGTYPE_ as CONFIGTYPE4_10_20_, delegation21_.PROCESSDEFINITION_ as PROCESSD5_10_20_ from AS400A.PAULN.JBPM_MODULEDEFINITION definition0_ left outer join AS400A.PAULN.JBPM_TASK task1_ on definition0_.STARTTASK_=task1_.ID_ left outer join AS400A.PAULN.JBPM_PROCESSDEFINITION processdef2_ on task1_.PROCESSDEFINITION_=processdef2_.ID_ left outer join AS400A.PAULN.JBPM_NODE startstate3_ on processdef2_.STARTSTATE_=startstate3_.ID_ left outer join AS400A.PAULN.JBPM_PROCESSDEFINITION processdef4_ on startstate3_.PROCESSDEFINITION_=processdef4_.ID_ left outer join AS400A.PAULN.JBPM_ACTION action5_ on startstate3_.ACTION_=action5_.ID_ left outer join AS400A.PAULN.JBPM_ACTION action6_ on action5_.REFERENCEDACTION_=action6_.ID_ left outer join AS400A.PAULN.JBPM_DELEGATION delegation7_ on action6_.ACTIONDELEGATION_=delegation7_.ID_ left outer join AS400A.PAULN.JBPM_PROCESSDEFINITION processdef8_ on delegation7_.PROCESSDEFINITION_=processdef8_.ID_ left outer join AS400A.PAULN.JBPM_EVENT event9_ on action6_.EVENT_=event9_.ID_ left outer join AS400A.PAULN.JBPM_PROCESSDEFINITION processdef10_ on action6_.PROCESSDEFINITION_=processdef10_.ID_ left outer join AS400A.PAULN.JBPM_ACTION action11_ on action6_.TIMERACTION_=action11_.ID_ left outer join AS400A.PAULN.JBPM_NODE superstate12_ on startstate3_.SUPERSTATE_=superstate12_.ID_ left outer join AS400A.PAULN.JBPM_MODULEDEFINITION taskmgmtde13_ on task1_.TASKMGMTDEFINITION_=taskmgmtde13_.ID_ left outer join AS400A.PAULN.JBPM_NODE tasknode14_ on task1_.TASKNODE_=tasknode14_.ID_ left outer join AS400A.PAULN.JBPM_NODE startstate15_ on task1_.STARTSTATE_=startstate15_.ID_ left outer join AS400A.PAULN.JBPM_DELEGATION delegation16_ on task1_.ASSIGNMENTDELEGATION_=delegation16_.ID_ left outer join AS400A.PAULN.JBPM_SWIMLANE swimlane17_ on task1_.SWIMLANE_=swimlane17_.ID_ left outer join AS400A.PAULN.JBPM_DELEGATION delegation18_ on swimlane17_.ASSIGNMENTDELEGATION_=delegation18_.ID_ left outer join AS400A.PAULN.JBPM_MODULEDEFINITION taskmgmtde19_ on swimlane17_.TASKMGMTDEFINITION_=taskmgmtde19_.ID_ left outer join AS400A.PAULN.JBPM_TASKCONTROLLER taskcontro20_ on task1_.TASKCONTROLLER_=taskcontro20_.ID_ left outer join AS400A.PAULN.JBPM_DELEGATION delegation21_ on taskcontro20_.TASKCONTROLLERDELEGATION_=delegation21_.ID_ where definition0_.PROCESSDEFINITION_=? -- 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-541) integrate jbpm 3.1 into jboss head and the jboss-4.x branch

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-541?page=all ] Thomas Diesler resolved JBPM-541. --------------------------------- Resolution: Out of Date > integrate jbpm 3.1 into jboss head and the jboss-4.x branch > ----------------------------------------------------------- > > Key: JBPM-541 > URL: http://jira.jboss.com/jira/browse/JBPM-541 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Critical > > * include jbpm packages in the jboss repository > * check head of jboss if jbpm is deployed in it > * run the jboss overall test suite and make sure that deployment of jbpm doesn't break anything > Thomas Diesler's instructions: > #1 checkout the repository > > The repository is in CVS under the module repository.jboss.com whose contents > are pushed to the http://repository.jboss.com site. > > export CVSROOT= :ext:tdiesler@cvs.forge.jboss.com:/cvsroot/jboss > cvs co repository.jboss.com > > #2 add the jBPM version to the repository > > See for example how jboss/jbossws defines dependencies on other modules in the repository. > You want to define dependencies on all thirdparty libraries that jBPM uses. If they are not already in the repository you need to add them > > #3 commit your changes > > Get your self a cup of coffee and wait until jBPM shows up on the http://repository.jboss.com site > Meanwhile you can continue work by setting the JBOSS_REPOSITORY env variable to your local copy of the repository > > #4 modify jboss-head/build-thirdparty.xml > > When you build jboss, jBPM and all dependencies should be pulled from http://repository.jboss.com > I assume you know howto build jboss. If not, see > > JBoss Module Information > http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossASCVSModules > > The JBossBuild build system > http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossBuild > > #5 modify jboss-head/build.xml > > You want to have a jBPM section that installs the jbpm.sar into the all configuration > > #6 create jBPM integration tests > > In jboss-head/testsuite/src/main. Add the required descriptors to jboss-head/testsuite/src/resources > Modify jboss-head/testsuite/import/test-jars.xml, create a jbpm.xml section that builds the deployments. > > See how webservice tests build and deploy their tests ? do not introduce a dependency on a host particular host name > > #7 run tests-jbpm > > Modify jboss-head/testsuite/build.xml to contain a tests-jbpm target. Run that target and make sure all your integration tests pass. Add your target to the ?tests? target > > #8 checkout cruise control > > On day two, your tests should show up on http://cruisecontrol.jboss.com/cc/ jboss-head-testsuite-1.5 > If your tests still pass, celebrate that jBPM is now integrated into JBoss. > Good Luck > -thomas -- 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-472) jbpm-drools integration

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-472?page=all ] Thomas Diesler resolved JBPM-472. --------------------------------- Resolution: Out of Date > jbpm-drools integration > ----------------------- > > Key: JBPM-472 > URL: http://jira.jboss.com/jira/browse/JBPM-472 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Critical > > 1) using the process variables as facts in JBoss Rules. Potentially, all SEAM context variables could be useful as facts... > 2) decision nodes making a choice in the process based on rules and the process data. > 3) assignment of actors (resources like people, groups or systems) to tasks. > 4) extracting rules from the process so that they are evaluated after each state change of the process. -- 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-474) finalize the second level cache configuration

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-474?page=all ] Thomas Diesler resolved JBPM-474. --------------------------------- Resolution: Out of Date > finalize the second level cache configuration > --------------------------------------------- > > Key: JBPM-474 > URL: http://jira.jboss.com/jira/browse/JBPM-474 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > in the hibernate tuning session, it turned out that we also have to enable the second level cache for the collections in the process definition model. -- 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