April 2010 - jbpm-issues - Jboss List Archives

[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

14 years, 5 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

14 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBPM-2848) Stop Tomcat Ant task fails, catalina.bat not found

by David Olivan Ubieto (JIRA)

Stop Tomcat Ant task fails, catalina.bat not found -------------------------------------------------- Key: JBPM-2848 URL: https://jira.jboss.org/jira/browse/JBPM-2848 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.3 Environment: Windows XP SP3 Professional, SUN Java 1.6.0_10, Ant 1.7.0, jBPM 4.3 Reporter: David Olivan Ubieto === Environment ============================== - jBPM Version : 4.3 - Database : Not relevant - JDK : SUN 1.6.0_10 - Container : Tomcat 6.0.20 - Configuration : As original - Libraries : As original === Process ================================== Not relevant === API =================================== Not relevant === Stacktrace ============================== Not relevant === Debug logs ============================== Not relevant. === Problem description ========================= Stop Tomcat Ant task failed as catalina.bat not found. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2634) New jBPM process definition in Eclipse generates xml with 4.0 namespace

by Joram Barrez (JIRA)

New jBPM process definition in Eclipse generates xml with 4.0 namespace ----------------------------------------------------------------------- Key: JBPM-2634 URL: https://jira.jboss.org/jira/browse/JBPM-2634 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.2 Reporter: Joram Barrez Assignee: Koen Aers Fix For: jBPM 4.x See title. The result is that you get an xml with a lot of warnings because the installed xsd is the 4.2 istead of the 4.0. -- 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, 5 months

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

14 years, 5 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

14 years, 5 months

5
13
0 / 0

[JBoss JIRA] Created: (JBPM-2806) Identity API doesn't allow access to parent field in Group

by Michele Mauro (JIRA)

Identity API doesn't allow access to parent field in Group ---------------------------------------------------------- Key: JBPM-2806 URL: https://jira.jboss.org/jira/browse/JBPM-2806 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.3 Reporter: Michele Mauro The Identity API does not have a method to access the parent of a Group. org.jbpm.api.identity.Group has only getId(), getName() and getType() methods. Probably this will be resolved with the integration of JBossIDM, but if the integration is not going to make it for 4.4, this one should be easy to fix alone by itself, since the column seems to be mapped and is present in the db. -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2714) fix hudson upgrade job

by Tom Baeyens (JIRA)

fix hudson upgrade job ---------------------- Key: JBPM-2714 URL: https://jira.jboss.org/jira/browse/JBPM-2714 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.4 we saw problems with it last iteration. analyse and fix those. also investigate if the test-upgrade project needs to be published for each release. http://repository.jboss.org/maven2/org/jbpm/jbpm4/jbpm-test-upgrade/ if so, make sure that is automatic in the future or added to the release guide. -- 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, 5 months

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-2627) Reporting on tomcat fails due to missing JNDI datasource configuration

by Heiko Braun (JIRA)

Reporting on tomcat fails due to missing JNDI datasource configuration ---------------------------------------------------------------------- Key: JBPM-2627 URL: https://jira.jboss.org/jira/browse/JBPM-2627 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Fix For: jBPM 4.2 Currently the report generation fails because there is no JBPM datasource configured in tomcat. Without the reports will be DB dependend and not work. In order to fix report generation on tomcat a proper JNDI datasource ('java:/JbpmDS') would need to be configured as described here: http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.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, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated

by Jan Scherf (JIRA)

With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated ----------------------------------------------------------------------------------------------------------- Key: JBPM-2765 URL: https://jira.jboss.org/jira/browse/JBPM-2765 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.3 Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables where created using the sql-scripts in ${jbpm.home}/install/src/db/create Reporter: Jan Scherf Fix For: jBPM 4.4 org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error. reason: - DatabaseIdComposer.createId(...) produces datatype string - but sql-Skripts create dbid-colums whose datatype is integer __________________________________________________________________________________________ See more Details on: http://community.jboss.org/message/521822 The reason of this problem can be found in org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid. Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml). As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String ... It seems that with the introduction of the id generator these scripts were not updated. -- 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, 5 months

4
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues April 2010