July 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBPM-1210) spring configuration support

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1210?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1210: ----------------------------------- Current state is that the basic persistence and transaction integration is done. The work done so far can be seen in test org.jbpm.pvm.api.spring.SpringTest and the corresponding resource file org/jbpm/pvm/api/spring/spring.beans.xml The current test shows that inside of the environment block, the spring transaction is active and that 2 subsequent fetches of the transactional hibernate session return the same object. Next task is that a process is deployed and executed. As that will require more objects to be configured in the spring xml. For each object that is needed, we'll have to see how constructors and setters will have to be added for the object to be easily configurable in spring. > spring configuration support > ---------------------------- > > Key: JBPM-1210 > URL: https://jira.jboss.org/jira/browse/JBPM-1210 > Project: JBoss jBPM > Issue Type: Feature Request > Components: PVM > Reporter: Tom Baeyens > Assignee: Mauricio Salatino > > The first goal is to create an EnvironmentFactory implementation that is based on spring configuration. > The class to complete is org.jbpm.pvm.internal.env.SpringEnvironmentFactory > The SpringEnvironmentFactory should relate to a spring ApplicationContext, I believe. The first thing to do is create a test that shows how a spring configuration can be used to create hibernate sessions. > Something like this: > static EnvironmentFactory environmentFactory = SpringEnvironmentFactory.parseResource("org/jbpm/pvm/spring/springbeans.xml"); > Environment environment = environmentFactory.openEnvironment(); > try { > Session hibernateSession = environment.get(Session.class); > assertNotNull(hibernateSession); > } finally { > environment.close(); > } -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1217) check collections if they need a presence boolean

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1217?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-1217: ------------------------------ Priority: Minor (was: Major) > check collections if they need a presence boolean > ------------------------------------------------- > > Key: JBPM-1217 > URL: https://jira.jboss.org/jira/browse/JBPM-1217 > Project: JBoss jBPM > Issue Type: Task > Components: PVM > Reporter: Tom Baeyens > Priority: Minor > > If in the code you need to know if there are elements in a collection, this will result into an extra query for the entities. If in most cases, the collection is empty, it might be an optimization to add a boolean pressence indicator next to the collection. The class could maintain that boolean to indicate if elements are available in the collection. That way, the extra query is saved if in the code you only need to do a collection-presence check. > For sure this is useful for the ProcessChanges. But probably for a lot of the other collections as well. > This shouldn't be applied blindfolded. Each case should be evaluated in terms of the number of times the presence check is executed in the code. -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1247) add mkdir to docbook target

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1247?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1247: ------------------------------ > add mkdir to docbook target > --------------------------- > > Key: JBPM-1247 > URL: https://jira.jboss.org/jira/browse/JBPM-1247 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Tom Baeyens > > the first time the ivy lib is downloaded, the directory is not created -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1221) split findAllJobs into findAllTimers and findAllMessages

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1221?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-1221: ------------------------------ Fix Version/s: PVM 1.0 alpha3 (was: PVM 1.0 beta1) > split findAllJobs into findAllTimers and findAllMessages > -------------------------------------------------------- > > Key: JBPM-1221 > URL: https://jira.jboss.org/jira/browse/JBPM-1221 > Project: JBoss jBPM > Issue Type: Task > Components: PVM > Reporter: Tom Baeyens > Assignee: Alejandro Guizar > Fix For: PVM 1.0 alpha3 > > > in PvmDbSession, the method findAllJobs is intended for the console tooling. i believe it's better to split it into findAllTimers and findAllMessages. > also the GetJobs command should be split similarly. -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1221) split findAllJobs into findAllTimers and findAllMessages

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1221?page=com.atlassian.jira.plug... ] Tom Baeyens resolved JBPM-1221. ------------------------------- Resolution: Done > split findAllJobs into findAllTimers and findAllMessages > -------------------------------------------------------- > > Key: JBPM-1221 > URL: https://jira.jboss.org/jira/browse/JBPM-1221 > Project: JBoss jBPM > Issue Type: Task > Components: PVM > Reporter: Tom Baeyens > Assignee: Alejandro Guizar > Fix For: PVM 1.0 beta1 > > > in PvmDbSession, the method findAllJobs is intended for the console tooling. i believe it's better to split it into findAllTimers and findAllMessages. > also the GetJobs command should be split similarly. -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1213) logging and history

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1213?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1213: ----------------------------------- First thing that we should do is define a simple history schema. Then then the proper logs should be generated from the execution so that the history database can be filled with it. > logging and history > ------------------- > > Key: JBPM-1213 > URL: https://jira.jboss.org/jira/browse/JBPM-1213 > Project: JBoss jBPM > Issue Type: Feature Request > Components: PVM > Reporter: Tom Baeyens > -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1213) logging and history

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1213?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-1213: ------------------------------ Priority: Critical (was: Major) > logging and history > ------------------- > > Key: JBPM-1213 > URL: https://jira.jboss.org/jira/browse/JBPM-1213 > Project: JBoss jBPM > Issue Type: Feature Request > Components: PVM > Reporter: Tom Baeyens > Priority: Critical > -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1213) logging and history

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1213?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1213: ----------------------------------- As part of this, an easy queryable basic history schema should be introduced > logging and history > ------------------- > > Key: JBPM-1213 > URL: https://jira.jboss.org/jira/browse/JBPM-1213 > Project: JBoss jBPM > Issue Type: Feature Request > Components: PVM > Reporter: Tom Baeyens > -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBPM-1229) check if CONDITION and CLIENT_API can be removed

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1229?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1229: ------------------------------ > check if CONDITION and CLIENT_API can be removed > -------------------------------------------------- > > Key: JBPM-1229 > URL: https://jira.jboss.org/jira/browse/JBPM-1229 > Project: JBoss jBPM > Issue Type: Task > Reporter: Tom Baeyens > > check if CONDITION and CLIENT_API can be removed from UserCodeType in ExecutionImpl -- 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

16 years, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1403) jBPM3 module ownership

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1403?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1403: --------------------------------- Security: Public (was: JBoss Internal) > jBPM3 module ownership > ---------------------- > > Key: JBPM-1403 > URL: https://jira.jboss.org/jira/browse/JBPM-1403 > Project: JBoss jBPM > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Productization > Reporter: Thomas Diesler > Assignee: Tom Baeyens > Fix For: JBossBPM-3.3.0 > > > I am in the search of component owners for these modules in jBPM3. Every component should be owned by a living soul that I can talk to if there is an issue with that module. > console > distribution (thomas) > enterprise > jbpm4jsf > jpdl/core > jpdl/db > jpdl/examples > jpdl/identity > jpdl/simulation > jpdl/userguide (tom) > jpdl/ws (heiko) > I filled in the owners for the modules that I know of. Please provide the missing information. -- 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

16 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2008