June 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2699) Expand query API test coverage

by Joram Barrez (JIRA)

Expand query API test coverage ------------------------------ Key: JBPM-2699 URL: https://jira.jboss.org/jira/browse/JBPM-2699 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Joram Barrez Fix For: jBPM 4.4 Currently, only basic usage is tested (ie non-chained queries mostly). This must be expanded in the future to enlarge the coverage and also to coverage the chaining. -- 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, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPM-2069) IntegerToLongConverter not consistent when dealing with null-values

by Hans Huber (JIRA)

IntegerToLongConverter not consistent when dealing with null-values ------------------------------------------------------------------- Key: JBPM-2069 URL: https://jira.jboss.org/jira/browse/JBPM-2069 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.2.5 GA Reporter: Hans Huber Priority: Minor org.jbpm.context.exe.converter.IntegerToLongConverter.supports(Object) return true for null values. org.jbpm.context.exe.converter.IntegerToLongConverter.convert(Object) on the other hand throws a NPE when a null value is passed in. i found this inconsistency when i tried to null a previously set variable with executionContext.setVariable("foobar", new Long(1)); executionContext.setVariable("foobar", null); -- 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, 9 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-2887) Extension to EL : possibility to add some custom function in juel

by Jaber C. Mourad (JIRA)

Extension to EL : possibility to add some custom function in juel ----------------------------------------------------------------- Key: JBPM-2887 URL: https://jira.jboss.org/browse/JBPM-2887 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Reporter: Jaber C. Mourad Fix For: jBPM 4.4 For some specific needs, I want being able to add some function in EL context. As juel accept it, it would be good to access to that feature and inject new functions... It would be helpful to add for example access to i18n context in mail activity... Regards -- 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

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2764) extend API to make it possible to determine the type of an active activity

by Sebastian Schneider (JIRA)

extend API to make it possible to determine the type of an active activity -------------------------------------------------------------------------- Key: JBPM-2764 URL: https://jira.jboss.org/jira/browse/JBPM-2764 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.0, jBPM 4.1, jBPM 4.2, jBPM 4.3 Environment: not relevant Reporter: Sebastian Schneider Fix For: jBPM 4.x The API should be extended in that way that you can easily determine the type of an active activity. To achieve this getActiveActivities() could be extended to also return the type of an activity additionally to its name and description. Or there could be a method taking an activity's name and returning its type. -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-2658) Process variables of type hibernate-long-id/hibernate-string-id don't work

by Derek Cornelius (JIRA)

Process variables of type hibernate-long-id/hibernate-string-id don't work -------------------------------------------------------------------------- Key: JBPM-2658 URL: https://jira.jboss.org/jira/browse/JBPM-2658 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.2 Reporter: Derek Cornelius This is the same problem as JBPM-2474. The problem is in HibernateIdMatcher. if (sessionFactory!=null) { ClassMetadata classMetadata = sessionFactory.getClassMetadata(value.getClass()); matches = ( (classMetadata!=null) && (classMetadata.getIdentifierType().getClass()==getIdType()) ); } value.getClass() is returning the Javassist proxy class that is not found. It needs to check for "value.getClass().getSuperClass()" if value instance of HibernateProxy. -- 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, 9 months

5
4
0 / 0

[JBoss JIRA] Created: (JBPM-1992) Logging is missing if JobExecutorThread marks TX as rollbackonly because of max

by Roman Heinz (JIRA)

Logging is missing if JobExecutorThread marks TX as rollbackonly because of max ------------------------------------------------------------------------------- Key: JBPM-1992 URL: https://jira.jboss.org/jira/browse/JBPM-1992 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA Reporter: Roman Heinz If the execution of an action/script/... takes longer than the time configured org.jbpm.job.executor.JobExecutor.maxLockTime, the current TX is marked as rollback-only without any logging. In JobExecutorThread: // if this job is locked too long long totalLockTimeInMillis = System.currentTimeMillis() - job.getLockTime().getTime(); if (totalLockTimeInMillis>maxLockTime) { jbpmContext.setRollbackOnly(); } Logging is missing to inform about the jbpmContext.setRollbackOnly() together with the reason. -- 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, 9 months

4
5
0 / 0

[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

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

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

13 years, 9 months

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

13 years, 10 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2010