July 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2873) Nice to have LIKE opertator support for Query objects

by Thomas Victor (JIRA)

Nice to have LIKE opertator support for Query objects ----------------------------------------------------- Key: JBPM-2873 URL: https://jira.jboss.org/browse/JBPM-2873 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Thomas Victor Priority: Optional Process engine has a user supplied keys. In our application we were using certain patters for the keys. For example our keys were like 5-1, 5-2 etc. It will be nice to have a support for querying processes which has key like '5-%'. It will be nice if all the query objects supports like operator. Please see the JIRA issue also https://jira.jboss.org/browse/JBPM-2868 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
16
0 / 0

[JBoss JIRA] Created: (JBPM-2398) expose full history details through the history api

by Tom Baeyens (JIRA)

expose full history details through the history api --------------------------------------------------- Key: JBPM-2398 URL: https://jira.jboss.org/jira/browse/JBPM-2398 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 expose the history that is in the database through the api -- 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

5
25
0 / 0

[JBoss JIRA] Created: (JBPM-2868) Add a new method 'processDefinitionIdLike' to TaskQuery

by Stephane Malbequi (JIRA)

Add a new method 'processDefinitionIdLike' to TaskQuery ------------------------------------------------------- Key: JBPM-2868 URL: https://jira.jboss.org/browse/JBPM-2868 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Reporter: Stephane Malbequi Priority: Minor Hi, it's not possible to create a task query to find all tasks of all versions of a specific process because TaskQuery append a where clause with a = operator and not a like operator if (processDefinitionId!=null) { appendWhereClause("task.processInstance.processDefinitionId = '"+processDefinitionId+"' ", hql); } May be, it's a good idea to add a new method like 'processDefinitionIdLike' to TaskQuery object in order to append a where clause like that : if (processDefinitionIdLike!=null) { appendWhereClause("task.processInstance.processDefinitionId like '"+processDefinitionIdLike+"' ", hql); } Another method to add should be : 'assigneeIn' in order to append a where clause like that : if (assigneeIn!=null && !assigneeIn.isEmpty()) { appendWhereClause("task.processInstance.assignee in ... } Thanks in advance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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-2908) Creating JbpmConfiguration with a different jbpm.cfg.xml in an action handler causes StackOverflowError

by Toshiya Kobayashi (JIRA)

Creating JbpmConfiguration with a different jbpm.cfg.xml in an action handler causes StackOverflowError ------------------------------------------------------------------------------------------------------- Key: JBPM-2908 URL: https://jira.jboss.org/browse/JBPM-2908 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 3.2.9 Environment: SOA-P 4.3.0 CP04 Reporter: Toshiya Kobayashi I tried to switch jbpm.cfg.xml (= create JbpmConfiguration with a different jbpm.cfg.xml) and start a process instance in my action handler. Client: 1. Create a JbpmConfiguration with "jbpm.1.cfg.xml" 2. Create a JbpmContext with the JbpmConfiguration(jbpm.1.cfg.xml) 3. Create and start a process instance Action handler of the process: 4. Create JbpmConfiguration instance with "jbpm.2.cfg.xml" 5. Create a JbpmContext with the JbpmConfiguration(jbpm.2.cfg.xml) 6. jbpmContext.getGraphSession() causes infinite loop and ends up with StackOverFlowError Caused by: java.lang.StackOverflowError at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:210) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65) at org.apache.log4j.Category.callAppenders(Category.java:203) at org.apache.log4j.Category.forcedLog(Category.java:388) at org.apache.log4j.Category.log(Category.java:853) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.logging.impl.Log4jProxy.log(Log4jProxy.java:311) at org.apache.commons.logging.impl.Log4jProxy.info(Log4jProxy.java:273) at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:150) at org.hibernate.cfg.Configuration.configure(Configuration.java:1432) at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:69) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:97) at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:94) at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:99) at org.jbpm.persistence.db.DbPersistenceService.getGraphSession(DbPersistenceService.java:330) at org.jbpm.JbpmContext.getGraphSession(JbpmContext.java:618) at org.jbpm.instantiation.ProcessClassLoader.getProcessDefinition(ProcessClassLoader.java:57) at org.jbpm.instantiation.ProcessClassLoader.findResource(ProcessClassLoader.java:63) at java.lang.ClassLoader.getResource(ClassLoader.java:958) at java.lang.ClassLoader.getResourceAsStream(ClassLoader.java:1148) at org.apache.xerces.parsers.SecuritySupport$6.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at org.apache.xerces.parsers.SecuritySupport.getResourceAsStream(Unknown Source) at org.apache.xerces.parsers.ObjectFactory.findJarServiceProvider(Unknown Source) at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source) at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source) at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:51) at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:187) at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:150) at org.dom4j.io.SAXHelper.createXMLReader(SAXHelper.java:83) at org.dom4j.io.SAXReader.createXMLReader(SAXReader.java:894) at org.dom4j.io.SAXReader.getXMLReader(SAXReader.java:715) at org.dom4j.io.SAXReader.read(SAXReader.java:435) at org.hibernate.cfg.Configuration.doConfigure(Configuration.java:1490) at org.hibernate.cfg.Configuration.configure(Configuration.java:1434) at org.jbpm.db.hibernate.HibernateHelper.createConfiguration(HibernateHelper.java:89) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getConfiguration(DbPersistenceServiceFactory.java:69) at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:97) at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:94) at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:99) at org.jbpm.persistence.db.DbPersistenceService.getGraphSession(DbPersistenceService.java:330) at org.jbpm.JbpmContext.getGraphSession(JbpmContext.java:618) ... How to reproduce: - Start SOA-P 4.3 CP04 - download and unzip reproducer.zip - copy jbpm.1.cfg.xml and jbpm.2.cfg.xml to <SOA_HOME>/jbossas/server/<config>/deploy/jbpm.esb - cd ProcessDefinitions - modify build.properties - ant deploypar - cd .. - cd ProcessCallWS - modify build.properties - ant deploy - ant run # jbpm.1.cfg.xml and jbpm.2.cfg.xml have same contents as this is a test reproducer Analysis: As the context classloader is ProcessClassLoader in action handler execution, JbpmContext.getGraphSession() -> org.hibernate.cfg.Configuration.configure() let ProcessClassLoader find resources, but ProcessClassLoader invokes JbpmContext.getGraphSession() recursively. Once DbPersistenceServiceFactory builds SessionFactory, the loop won't happen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPM-2876) Password encoding for login to console

by M M (JIRA)

Password encoding for login to console -------------------------------------- Key: JBPM-2876 URL: https://jira.jboss.org/browse/JBPM-2876 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.3 Reporter: M M When logging into the console, if a user's password includes a '%' (percent) symbol, the following error shows up in the server log and GWT shows an "authentication failed" error message. 06-01 12:03:22,412 WARN [org.apache.tomcat.util.http.Parameters] (http-stinger%2F10.20.36.59-8080-1) Parameters: Character decoding failed. Parameter skipped. java.io.CharConversionException: isHexDigit at org.apache.tomcat.util.buf.UDecoder.convert(UDecoder.java:88) at org.apache.tomcat.util.buf.UDecoder.convert(UDecoder.java:49) at org.apache.tomcat.util.http.Parameters.urlDecode(Parameters.java:429) at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:412) at org.apache.tomcat.util.http.Parameters.processParameters(Parameters.java:363) at org.apache.catalina.connector.Request.parseParameters(Request.java:2562) at org.apache.catalina.connector.Request.getParameter(Request.java:1060) at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:254) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:417) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Here are some relevant links: http://ninadgawad.wordpress.com/2008/08/21/character-decoding-error-while... http://www.mail-archive.com/users@tomcat.apache.org/msg36743.html http://www.mail-archive.com/users@tomcat.apache.org/msg36744.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPM-2769) Add FreeMarker support for mail templates

by Peter Horvath (JIRA)

Add FreeMarker support for mail templates ----------------------------------------- Key: JBPM-2769 URL: https://jira.jboss.org/jira/browse/JBPM-2769 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.x Reporter: Peter Horvath JBPM already uses FreeMarker to generate task forms. It would be great if FreeMarker could be used as a mail template engine as well. -- 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
3
0 / 0

[JBoss JIRA] Created: (JBPM-2858) migrate enterprise tests to cactus maven2 plugin

by Alejandro Guizar (JIRA)

migrate enterprise tests to cactus maven2 plugin ------------------------------------------------ Key: JBPM-2858 URL: https://jira.jboss.org/jira/browse/JBPM-2858 Project: jBPM Issue Type: Task Components: Runtime Engine Reporter: Alejandro Guizar Assignee: Alejandro Guizar Priority: Minor Fix For: jBPM 3.2.x Currently enterprise tests are carried out in a very ad-hoc manner. The project should take advantage of readily available maven2 plugins to conduct tests more orderly. http://jakarta.apache.org/cactus/integration/maven2/index.html -- 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

1
4
0 / 0

[JBoss JIRA] Created: (JBPM-2889) let timer support CRON

by Huisheng Xu (JIRA)

let timer support CRON ---------------------- Key: JBPM-2889 URL: https://jira.jboss.org/browse/JBPM-2889 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.3 Reporter: Huisheng Xu Fix For: jBPM 4.x Trigger timer every 1st day of the month HI all, How can I trigger a timer at first day every month at 4am? It seems the timer is configured to trigger Process deploy date + X time in the future but I really need to trigger timer in specific dates and hours regardless when the process has been deployed or the applications server has been started. Thanks, Davi -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/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-2417) allow for programmatic way to specify authentication through service api

by Tom Baeyens (JIRA)

allow for programmatic way to specify authentication through service api ------------------------------------------------------------------------ Key: JBPM-2417 URL: https://jira.jboss.org/jira/browse/JBPM-2417 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Engine Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.1 first target is our own console. our own console should pass the authentication information through the api. maybe this can be part of the more general: User provided transactional resources -- 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
9
0 / 0

[JBoss JIRA] Created: (JBPM-2568) review history based on user feedback

by Tom Baeyens (JIRA)

review history based on user feedback ------------------------------------- Key: JBPM-2568 URL: https://jira.jboss.org/jira/browse/JBPM-2568 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Fix For: jBPM 4.3 Ronald mentioned a lot of questions and activity around history. This issue is a reminder that we have to look into this topic in the 4.3 jira period (1st half of november) https://jira.jboss.org/jira/sr/jira.issueviews:searchrequest-printable/te... We should try to get an overview of what exactly the history related questions/issues are and find out how we can address them. Then translate that into concrete jira issues that can be prioritized. -- 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
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2010