October 2009 - jbpm-issues - Jboss List Archives

[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

13 years, 10 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

13 years, 10 months

3
5
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

13 years, 10 months

2
1
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

13 years, 10 months

4
7
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

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2573) Process name text input field in properties view does not input characters in the right order

by Carl Allain (JIRA)

Process name text input field in properties view does not input characters in the right order --------------------------------------------------------------------------------------------- Key: JBPM-2573 URL: https://jira.jboss.org/jira/browse/JBPM-2573 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: GPD Affects Versions: jBPM 4.1 Environment: Eclipse Platform 3.5.1.M20090917-0800 jBPM 4 Graphical Editor and Tools 1.1.0.v200908252230-31-8s733L3J7D7793 All jBPM 4 Tools Features 4.1.0.v200908252230-775-A0I8_GOdN2MrX_LVTDTlIAAj jBPM 4 Graphical Editor and Tools Sources 1.1.0.v200908252230-31-8s733L3J7D7793 Windows XP SP3 Reporter: Carl Allain Priority: Minor The field "name" in the "properties" view does not work like other fields. Characters entered on the keyboard are always put at the beginning of the current property value, regardless of where the cursor is positionned. -- 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

13 years, 11 months

5
4
0 / 0

[JBoss JIRA] Created: (JBPM-2434) Write jBPM4 article

by Joram Barrez (JIRA)

Write jBPM4 article ------------------- Key: JBPM-2434 URL: https://jira.jboss.org/jira/browse/JBPM-2434 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Joram Barrez Assignee: Joram Barrez Fix For: jBPM 4.1 Write a general article explaining what jBPM4 is, why and when you should use it. Also think about a valid use case that shows the value of using jBPM4. -- 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

13 years, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (JBPM-1768) fix groovy expression support

by Tom Baeyens (JIRA)

fix groovy expression support ----------------------------- Key: JBPM-1768 URL: https://jira.jboss.org/jira/browse/JBPM-1768 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.0.0 Alpha2 Fix test GroovyExpressionTest It's a matter of getting the right dependencies defined in maven. -- 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

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1775) verify if collection exceptionHandlers can be loaded lazy

by Tom Baeyens (JIRA)

verify if collection exceptionHandlers can be loaded lazy --------------------------------------------------------- Key: JBPM-1775 URL: https://jira.jboss.org/jira/browse/JBPM-1775 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 3.3.1 GA >From Martin Putz: " A quick test showed that setting all those relations to lazy="true" cuts down the number of executed SQL selects quite drastically. I don't see any negative side effects of changing these settings, but I'm curious about the reasons why lazy="false" is chosen as default. Especially as I don't see a lot of our customers using exception handlers (or at least they don't report it). Regards, Martin " -- 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

13 years, 11 months

5
13
0 / 0

[JBoss JIRA] Created: (JBPM-2482) console should pass authenticated user to engine operations

by Tom Baeyens (JIRA)

console should pass authenticated user to engine operations ----------------------------------------------------------- Key: JBPM-2482 URL: https://jira.jboss.org/jira/browse/JBPM-2482 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Tom Baeyens Assignee: Joram Barrez Fix For: jBPM 4.2 following pieces of console code should be revisisted so that the authenticated user is passed to the engine operations: public ProcessInstanceRef newInstance(String definitionId, Map<String, Object> processVars) { Environment env = ((EnvironmentFactory)processEngine).openEnvironment(); try { ExecutionService execService = this.processEngine.getExecutionService(); Execution exec = execService.startProcessInstanceById(definitionId); execService.setVariables(exec.getId(), processVars); return ModelAdaptor.adoptExecution((ExecutionImpl)exec); } finally{ env.close(); } } First, the API needs to expose a way on how to set the authenticated user programmatically. -- 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

13 years, 11 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2009