January 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2473) description about coexistence of version and binding attribute for sub-process is wrong

by Toshiya Kobayashi (JIRA)

description about coexistence of version and binding attribute for sub-process is wrong ---------------------------------------------------------------------------------------- Key: JBPM-2473 URL: https://jira.jboss.org/jira/browse/JBPM-2473 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.5.SP5 Reporter: Toshiya Kobayashi Priority: Minor 21.4.28. sub-process When both version and binding="late" are given then jBPM will use the version as requested, but will not yet try to find the sub process when the parent process-state is deployed. http://docs.jboss.org/jbpm/v3.2/userguide/html_single/index.html#subproce... But actually, ProcessState.execute() ignores version attribute if binding="late". So fix the description to: When both version and binding="late" are given then jBPM will ignore the version attribute and use the latest version. -- 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

14 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2386) Update description of DeployProcessTask

by Toshiya Kobayashi (JIRA)

Update description of DeployProcessTask --------------------------------------- Key: JBPM-2386 URL: https://jira.jboss.org/jira/browse/JBPM-2386 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.5.SP5 Reporter: Toshiya Kobayashi Chapter 21.1.1 of the User Guide states: ============ <target name="deploy.par"> <taskdef name="deploypar" classname="org.jbpm.ant.DeployProcessTask"> <classpath --make sure the jbpm-[version].jar is in this classpath--/> </taskdef> <deploypar par="build/myprocess.par" /> </target> To deploy more process archives at once, use the nested fileset elements. The file attribute itself is optional. Other attributes of the ant task are: * cfg: cfg is optional, the default value is 'hibernate.cfg.xml'. The hibernate configuration file that contains the jdbc connection properties to the database and the mapping files. * properties: properties is optional and overwrites *all* hibernate properties as found in the hibernate.cfg.xml * createschema: if set to true, the jbpm database schema is created before the processes get deployed. ============ http://docs.jboss.org/jbpm/v3.2/userguide/html_single/#theprocessarchive But this description is old now. They should be: ============= <target name="deploy.par"> <taskdef name="deploypar" classname="org.jbpm.ant.DeployProcessTask"> <classpath --ensure jbpm-[version].jar is in this classpath--/> </taskdef> <deploypar process="build/myprocess.par" /> </target> To deploy more process archives at once, use the nested fileset elements. The process attribute itself is optional. Other attributes of the ant task are: * jbpmcfg: Optional, the default value is jbpm.cfg.xml. The JBPM configuration file can specify the location of Hibernate configuration file ( the default value is hibernate.cfg.xml ) that contains the jdbc connection properties to the database and the mapping files. ============= -- 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

14 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBPM-2530) Add SLF4J support to allow plugging in any logging framework

by Peter Horvath (JIRA)

Add SLF4J support to allow plugging in any logging framework ------------------------------------------------------------ Key: JBPM-2530 URL: https://jira.jboss.org/jira/browse/JBPM-2530 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Peter Horvath Adding SLF4J logging support would make it possible to plug in any Logging framework to jBPM without any further code modification. Adding a wrapper for SLF4J org.slf4j.Logger and org.slf4j.LoggerFactory to org.jbpm.internal.log.Log class (similarly to the current Log4j implementation) would be trivial to implement and would provide an extremely powerful logging system to jBPM. -- 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

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2706) Add subprocess with timers and wait state to test case suite

by Martin Porter (JIRA)

Add subprocess with timers and wait state to test case suite ------------------------------------------------------------ Key: JBPM-2706 URL: https://jira.jboss.org/jira/browse/JBPM-2706 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.x Reporter: Martin Porter Cleanup and add the attached test case for simple subprocess with custom java command exector and timeout loop for regression testing. -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2405) make task forms i18n-able

by Tom Baeyens (JIRA)

make task forms i18n-able ------------------------- Key: JBPM-2405 URL: https://jira.jboss.org/jira/browse/JBPM-2405 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console, Runtime Engine Reporter: Tom Baeyens Fix For: jBPM 4.x gert, can you try and see where we need to update the engine in order to accomodate this -- 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

14 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2773) TaskService: allow search for assigned candidate tasks

by Kai WeingÃ¤rtner (JIRA)

TaskService: allow search for assigned candidate tasks ------------------------------------------------------ Key: JBPM-2773 URL: https://jira.jboss.org/jira/browse/JBPM-2773 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Environment: any Reporter: Kai WeingÃ¤rtner Fix For: jBPM 4.x I would like to be able to find all tasks a user is a candidate for, regardless of the task being assigned or not. Currently the TaskQuery.candidate - filter also sets the unassigned filter. Thus, already assigned candidate tasks can never be found. Possible use cases: - a task needs to be reassigned due to sickness of the assignee - user A needs to take user B's task, when a customer approaches user A about a task concerning him Solution: - don't add the unassigned filter in the candidate filter of TaskQuery but make them separate. To achieve the current result, one could set both filters explicitly. -- 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

14 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-2759) Make duedate accept subtractions with EL and business duration

by Ronald van Kuijk (JIRA)

Make duedate accept subtractions with EL and business duration --------------------------------------------------------------- Key: JBPM-2759 URL: https://jira.jboss.org/jira/browse/JBPM-2759 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0, jBPM 4.1, jBPM 4.2, jBPM 4.3 Reporter: Ronald van Kuijk Priority: Minor Subtraction in combination with EL is not implemented. See JBPM-2745 (not was it in jBPM 3: JBPM-1776 so it is no regression) -- 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

14 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (JBPM-2585) review / cleanup ExpressionEvaluatorDescriptor

by Tom Baeyens (JIRA)

review / cleanup ExpressionEvaluatorDescriptor ---------------------------------------------- Key: JBPM-2585 URL: https://jira.jboss.org/jira/browse/JBPM-2585 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.2 see if it can be removed or make a jira issue to remove it in one of the next versions -- 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

14 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-2753) Simplify map specification in jPDL for simple case

by M M (JIRA)

Simplify map specification in jPDL for simple case -------------------------------------------------- Key: JBPM-2753 URL: https://jira.jboss.org/jira/browse/JBPM-2753 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.2 Reporter: M M Allow simpler specification of maps in the case where both the key and value are strings, by allowing key and value to be specified as attributes of the <entry> element, instead of as child elements. This will greatly reduce the verbosity of the XML for this common case. The following <custom class="com.company.CustomActivity" name="some_step"> <property name="inputs"> <map> <entry> <key> <string value="input_file_a" /> </key> <value><string value="some_filename" /></value> </entry> <entry> <key> <string value="another_input" /> </key> <value><string value="1234" /></value> </entry> </map> </property> <transition to="next_thing"/> </custom> would become simpler, as <custom class="com.company.CustomActivity" name="some_step"> <property name="inputs"> <map> <entry key="input_file_a" value="some_filename" /> <entry key="another_input" value="1234" /> </map> </property> <transition to="next_thing"/> </custom> -- 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

14 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2605) DbPersistenceServiceFactory should not close SessionFactory if it didn't opened it

by Stefano Travelli (JIRA)

DbPersistenceServiceFactory should not close SessionFactory if it didn't opened it ---------------------------------------------------------------------------------- Key: JBPM-2605 URL: https://jira.jboss.org/jira/browse/JBPM-2605 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.7 Environment: JBoss 4.2.3, Seam 2.1 Reporter: Stefano Travelli I configure JBpm with Seam 2.1 so that the JBpm SessionFactory is the same of the underlying SessionFactory used by the EntityManagerFactory in JPA. In order to do so I include JBpm hibernate.cfg.xml in the persistence-unit. Then I declare the JNDI name in jbpm.cfg.xml: <persistence-unit name="getin"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>java:/getinDS</jta-data-source> <propertyies>  <property name="hibernate.session_factory_name" value="java:/getinSessionFactory"/> <property name="hibernate.ejb.cfgfile" value="jbpm.hibernate.cfg.xml"/> </properties> </persistence-unit> <jbpm-configuration> <jbpm-context> <service name="persistence"> <factory> <bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory"> <field name="isTransactionEnabled"> <false/> </field> <field name="sessionFactoryJndiName"> <string value="java:/getinSessionFactory"/> </field> </bean> </factory> </service> <service name="tx" factory="org.jbpm.tx.TxServiceFactory"/> <service name="message" factory="org.jbpm.msg.db.DbMessageServiceFactory"/> <service name="scheduler" factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory"/> <service name="logging" factory="org.jbpm.logging.db.DbLoggingServiceFactory"/> <service name="authentication" factory="org.jbpm.security.authentication.DefaultAuthenticationServiceFactory"/> </jbpm-context> </jbpm-configuration> It works fine except that during test execution in the Seam enviroment JBpm context is opened and closed several times while the persistence unit stays. However, as a JBpm context closes, DbPersistenceServiceFactory also closes the SessionFactory invalidating the EntityManagerFactory. When DbPersistenceServiceFactory doesn't create the SessionFactory taking it from JNDI, it shouldn't close it as this should be a responsibility of the component who registered it in JNDI in first place. The patch is simple: public void close() { if (sessionFactory != null && sessionFactoryJndiName == null) { log.debug("closing hibernate session factory"); sessionFactory.close(); } } -- 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

14 years, 4 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2010