June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-396) Queries generated via hibernate are not compatible with Db2 for iSeries

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-396?page=all ] Thomas Diesler resolved JBPM-396. --------------------------------- Resolution: Out of Date > Queries generated via hibernate are not compatible with Db2 for iSeries > ----------------------------------------------------------------------- > > Key: JBPM-396 > URL: http://jira.jboss.com/jira/browse/JBPM-396 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Environment: Windows, DB2 UDB for iSeries > Reporter: Paul Newport > Assigned To: Tom Baeyens > > Essentially the problem is that because the hibernate mapping files specify column lengths for some string fields as 4000, these get created as varchars on the iSeries, as the iSeries varchar maximum is just under 32k. > If JBPM does a query that results in many individual 4000 long varchars being requested to be returned, this blows DB2's limit of 32k for a result set width (ie, the sum of the column lengths for each non LOB column). > The solution to this is to specific an SQL type on the mapping files, so as to force the generatiion of TEXT/CLOB fields in the generated database. > An alternative is to look at any string defined as 4000 and re-assess theses lengths. Is 4000 always needed ? I suspect not, and if it is, might not sometimes 4001 or greater be needed ? One could probably get away with reducing many of these string lengths, but by makign them all CLOBs anyway, yo do not have to wory about ever blowing the current 4000 byte limit, and you solve the iSeries DB2 problem as well. > PS as iSeries are not machines you tend to have lying around to test on, I can test any changes needed for the project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-365) Documentation - Incomplete sentence

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-365?page=all ] Thomas Diesler resolved JBPM-365. --------------------------------- Resolution: Out of Date > Documentation - Incomplete sentence > ------------------------------------ > > Key: JBPM-365 > URL: http://jira.jboss.com/jira/browse/JBPM-365 > Project: JBoss jBPM > Issue Type: Bug > Components: Documentation > Reporter: schwettmann > Assigned To: Tom Baeyens > Priority: Minor > > http://docs.jboss.com/jbpm/v3/userguide/jpdl.html#variable.element > JBoss jBPM User Guide > JBoss jBPM 3.0 > Chapter 13.3.18 > the only access specifiers used so far are > bug : Incomplete sentence. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-372) Documentation - The "priority" attribute of a task should be described further.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-372?page=all ] Thomas Diesler resolved JBPM-372. --------------------------------- Resolution: Out of Date > Documentation - The "priority" attribute of a task should be described further. > ------------------------------------------------------------------------------- > > Key: JBPM-372 > URL: http://jira.jboss.com/jira/browse/JBPM-372 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Documentation > Reporter: schwettmann > Assigned To: Tom Baeyens > Priority: Minor > > http://docs.jboss.com/jbpm/v3/userguide/jpdl.html#task.element > JBoss jBPM User Guide > JBoss jBPM 3.0 > The priority attribute of a task should be described further. Either in chapter 13.3.23 or in chapter 9.1 > is described how this attribute is used. Only the range of the values is described. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-379) jBPM Scheduler component needs to have a (max) number of retries parameter added

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-379?page=all ] Thomas Diesler resolved JBPM-379. --------------------------------- Resolution: Out of Date > jBPM Scheduler component needs to have a (max) number of retries parameter added > -------------------------------------------------------------------------------- > > Key: JBPM-379 > URL: http://jira.jboss.com/jira/browse/JBPM-379 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Environment: The jBPM scheduler > Reporter: Alisdair Feint > Assigned To: Tom Baeyens > Priority: Minor > > The jBPM scheuler needs to have the number of retries as a configurable parameter. This should be specified in the process definition, as well as in the scheduler API -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-346) scope of nodes in process definition mixed with superstates does not work

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-346?page=all ] Thomas Diesler resolved JBPM-346. --------------------------------- Resolution: Out of Date > scope of nodes in process definition mixed with superstates does not work > ------------------------------------------------------------------------- > > Key: JBPM-346 > URL: http://jira.jboss.com/jira/browse/JBPM-346 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Reporter: James Depoorter > Assigned To: Tom Baeyens > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Re-using the same nodenames within different scopes (root process definition and superstates) gives errors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-301) Update JbpmSession javadocs

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-301?page=all ] Thomas Diesler resolved JBPM-301. --------------------------------- Resolution: Out of Date > Update JbpmSession javadocs > --------------------------- > > Key: JBPM-301 > URL: http://jira.jboss.com/jira/browse/JBPM-301 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 > Reporter: Daniel Serodio > Assigned To: Tom Baeyens > Priority: Optional > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > JbpmSession javadocs say: > "represents the connection to the jbpm database. > * You can obtain a DbSession with ..." > It looks like JbpmSession used to be called DbSession but the Javadoc was not updated when the class was renamed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-304) Transient variables are not available in scripts

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-304?page=all ] Thomas Diesler resolved JBPM-304. --------------------------------- Resolution: Out of Date > Transient variables are not available in scripts > ------------------------------------------------ > > Key: JBPM-304 > URL: http://jira.jboss.com/jira/browse/JBPM-304 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 > Reporter: Daniel Serodio > Assigned To: Tom Baeyens > Priority: Minor > > The jBPM documentation, section 7.4.5. Script, says: > "... By default, all process variables are available as script-variables and no script-variables will be written to the process variables." > But the transient variables are not available to <script>s, just to <action>s. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-309) Do not throw NullPointerException if delegation class is unknown

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-309?page=all ] Thomas Diesler resolved JBPM-309. --------------------------------- Resolution: Out of Date > Do not throw NullPointerException if delegation class is unknown > ---------------------------------------------------------------- > > Key: JBPM-309 > URL: http://jira.jboss.com/jira/browse/JBPM-309 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Reporter: Bernd Ruecker > Assigned To: Tom Baeyens > Priority: Optional > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > If we declare a action class in jBPM: > <transition name="xxxx"> > <action class="com.camunda.ccs.process.orderprocessing.OrderActions$PrintReceipts"/> > </transition> > And this class doesn't exist the follwoing exception is thrown: > Caused by: java.lang.NullPointerException > at org.jbpm.graph.def.Action.execute(Action.java:79) > at org.jbpm.graph.def.GraphElement.executeActions(GraphElement.java:186) > ... 26 more > I think, it would be much better to have a ClassNotFoundException! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-320) ExceptionHandler class not loaded by the ProcessClassLoader

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-320?page=all ] Thomas Diesler resolved JBPM-320. --------------------------------- Resolution: Out of Date > ExceptionHandler class not loaded by the ProcessClassLoader > ----------------------------------------------------------- > > Key: JBPM-320 > URL: http://jira.jboss.com/jira/browse/JBPM-320 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 > Environment: Win2K,Jboss-4.0.2,JBPM3.0 > Reporter: Ashwin Iyer > Assigned To: Tom Baeyens > Priority: Minor > > Hi , > I get a ClassLoaderException when trying to use the > <exception-handler exception-class="com.sample.exception.SblException> > The reason being: > The ExceptionHandler class does not use the process class loader when it loads the exception-class to verify it is assignable from the thrown exception. > Can you please look into this issue > Thanks > Ashwin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-315) SchedulerMain can not work

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-315?page=all ] Thomas Diesler resolved JBPM-315. --------------------------------- Resolution: Out of Date > SchedulerMain can not work > -------------------------- > > Key: JBPM-315 > URL: http://jira.jboss.com/jira/browse/JBPM-315 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Reporter: Bernd Ruecker > Assigned To: Tom Baeyens > Priority: Minor > Attachments: SchedulerMain.java > > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > SchedulerMain.main throws NullPointerException at line 29 > I think the order of the two lines are wrong: > // register the console listener > scheduler.getSchedulerThread().addListener(new LogListener()); > > // start the scheduler > scheduler.start(); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2008