February 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Deleted: (JBPM-1219) refactor unscalable methods in session interfaces and commands

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1219?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1219: ------------------------------ > refactor unscalable methods in session interfaces and commands > -------------------------------------------------------------- > > Key: JBPM-1219 > URL: https://jira.jboss.org/jira/browse/JBPM-1219 > Project: JBoss jBPM > Issue Type: Task > Reporter: Tom Baeyens > Assignee: Tom Baeyens > Priority: Critical > > currently there are methods like: > findProcessDefinitions(String name) and findAllJobs() in PvmDbSession > all the commands and interfaces should be reviewed and get some kind of paging mechanism for these queries. otherwise it's not scalable. in large deployments these methods will cause memory problems. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1414) documentation

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1414?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1414: ------------------------------ > documentation > ------------- > > Key: JBPM-1414 > URL: https://jira.jboss.org/jira/browse/JBPM-1414 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Priority: Critical > > The scope of the docs in this first version is flexible. But we should look at what is there now. And how we can shape that into something shippable. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1427) sanetize the reference manual

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1427?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1427: ------------------------------ > sanetize the reference manual > ----------------------------- > > Key: JBPM-1427 > URL: https://jira.jboss.org/jira/browse/JBPM-1427 > Project: JBoss jBPM > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Tom Baeyens > > reference manual should contain more background about the PVM. the architectural parts, the features, pluggability points and so on. > the reference manual should indicate what is in the core supported PVM and extension parts that are still in incubation. > everything which is documented already in the tutorial should not be duplicated in the reference manual (of course:-) -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1426) update tutorial

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1426?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1426: ------------------------------ > update tutorial > --------------- > > Key: JBPM-1426 > URL: https://jira.jboss.org/jira/browse/JBPM-1426 > Project: JBoss jBPM > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > > After the samples are updated, the tutorial should just take a user through the samples. The goal is to learn a user how to work with the services API to do the basic operations when using with a PVM based workflow engine. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1425) work out samples in the test suite

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1425?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1425: ------------------------------ > work out samples in the test suite > ---------------------------------- > > Key: JBPM-1425 > URL: https://jira.jboss.org/jira/browse/JBPM-1425 > Project: JBoss jBPM > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Tom Baeyens > > Tom will work out the samples based on the services. > The samples will be a set of tests that have as goal to show from simple to complex the main features in the PVM. This is done by using the services in a persistent environment as that is 90% of the target usage of the PVM. > The samples will be documented in the tutorial. -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1684) create test for DbSession methods

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1684?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1684: ------------------------------ > create test for DbSession methods > --------------------------------- > > Key: JBPM-1684 > URL: https://jira.jboss.org/jira/browse/JBPM-1684 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Priority: Critical > > Methods from base class DbSession should be tested or removed > void flush(); > void forceVersionUpdate(Object entity); > void lockPessimistically(Object entity); > Before you remove something, check if it is used :-) -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1860) introduce identity spi

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1860?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1860: ------------------------------ > introduce identity spi > ---------------------- > > Key: JBPM-1860 > URL: https://jira.jboss.org/jira/browse/JBPM-1860 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Tom Baeyens > > in jbpm 4 we should centralize all access to the identity component. this spi will be the jbpm pluggability point to replace identity components. > then we should bind this initially and by default to the new jboss identity component: > http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184053#4184053 -- 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

15 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1903) java:/comp/env JNDI Namespace not found within ActionHandler Implementations

by Robert Schmelzer (JIRA)

java:/comp/env JNDI Namespace not found within ActionHandler Implementations ---------------------------------------------------------------------------- Key: JBPM-1903 URL: https://jira.jboss.org/jira/browse/JBPM-1903 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.0 GA Environment: JBoss 4.2.3 GA with MySQL5 Database jBPM Enterprise Deployment Reporter: Robert Schmelzer When you try to lookup the JNDI Namespace java:comp/env in an enterprise deployment wihtin an ActionHandler implementation it will throw an NameNotFoundException. So it is not possible to lookup ejb or other component local stuff within ActionHandler implementations. In special this also affects you, when you signal a token within an ActionHandler and any of the following Node is async using the JMSMessgeService because the JMS implementation will also make a lookup on the connection factory using the comp/env Namespace. The reason for this is the change in the classloader when executing ActionHandlers. The contex class loader is by default changed to the ProcessClassLoader using the UCL as parent. But JBoss uses the ContextClassLoader ot scope the comp/env Namespace. When using the original context class loader as the parent for the ProcessClassLoader it works again. -- 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

15 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (JBPM-2007) SQL scripts in jbpm-sql missing identity table creation for most DB's.

by Julian Coleman (JIRA)

SQL scripts in jbpm-sql missing identity table creation for most DB's. ---------------------------------------------------------------------- Key: JBPM-2007 URL: https://jira.jboss.org/jira/browse/JBPM-2007 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.4 GA Environment: SOA platform 4.3.0 GA CP01 (CR1) Reporter: Julian Coleman Priority: Critical Fix For: jBPM-3.2.4.SP1 See SOA-1157 - when starting the SOA server for the second and subsequent times, the scripts attempt to recreate the DB, which fails, as the DB has already been created. The script is the ESB jbpm-service.xml script and it checks the existance of the JBPM_ID_USER table to see if the databases have already been created. In the (generated at build time) jbpm-sql/*sql scipts from 3.2.2, every DB contains: create tabe JBPM_ID_* lines, but these are missing from the source in 3.2.4. -- 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

15 years, 10 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues February 2009