July 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1431) make db for test suite runs configurable

by Tom Baeyens (JIRA)

make db for test suite runs configurable ---------------------------------------- Key: JBPM-1431 URL: https://jira.jboss.org/jira/browse/JBPM-1431 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens Assignee: Tom Baeyens This must enable the set up of the matrix hudson job that runs the db test suite on different databases. Ideally, the database name should be given as a property like this "mvn -Ddb=mysql-5 clean test" Another aspect is the naming convention of the DB tests. We should make sure that we can create a maven profile that only runs the DB tests. -- 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
1
0 / 0

[JBoss JIRA] Updated: (JBPM-1215) remove class ConfigurationFiles in test suite

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1215?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-1215: ------------------------------ Parent: JBPM-1430 Issue Type: Sub-task (was: Task) > remove class ConfigurationFiles in test suite > --------------------------------------------- > > Key: JBPM-1215 > URL: https://jira.jboss.org/jira/browse/JBPM-1215 > Project: JBoss jBPM > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: PVM > Reporter: Tom Baeyens > > it became redundant after the environment configuration files moved to the packages themselves. > verify with your IDE if it is still used before you remove it :-) -- 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-1281) create job executor test suite overview

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1281?page=com.atlassian.jira.plug... ] Tom Baeyens deleted JBPM-1281: ------------------------------ > create job executor test suite overview > --------------------------------------- > > Key: JBPM-1281 > URL: https://jira.jboss.org/jira/browse/JBPM-1281 > Project: JBoss jBPM > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Tom Baeyens > Assignee: Alejandro Guizar > > create a description of what will be tested and which interfaces will be used to do it -- 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] Assigned: (JBPM-1213) logging and history

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1213?page=com.atlassian.jira.plug... ] Tom Baeyens reassigned JBPM-1213: --------------------------------- Assignee: Guillaume Porcher > 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 > Assignee: Guillaume Porcher > 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: ----------------------------------- User interaction logs are kept for a second iteration. I (Tom) would like that to introduce a user interaction process log on the pvm, which is compatible with the roles in the task management component. I think it is possible to do it in a way that also would support the bonita use cases. Once the initial structure as described above is developed, I'll implement a proposal for the a user interaction base type. Basis that I currently have in mind is this: HistoryUserInteraction with properties: * a userId indicating the id of the user doing the operation * role: the role of the involved person (see task component and human interaction management) * property and a dynamic map of properties (Map<String,String>) > 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: ----------------------------------- in meeting with Guillaume we concluded the following a package org.jbpm.pvm.history will be created. it will have following main model classes: HistoryProcessInstance HistoryNode HistoryVariable : a history variable represents one variable for a process instance. it has a reference to the current HistoryVariableValue and a list of historical HistoryVariableValues HistoryVariableValue : contains one value that was in a variable at a given point in time the package will also contain a HistoryLogSession The history log session will have a map that maps process log classes to handlers. The handlers will be anonymous inner classes. For each incoming log, the HistoryLogSession will lookup the handler in the map and let it process the processlog. Processing the processlog means that the information will be integrated in the history model. The relation to specific activity information still needs to be worked out. One idea is to use a generic map of key-value pairs related to the HistoryNode. Another idea is to have a relation from the custom history table to the history node. In parallel with working out the model and the history log session, the queries need to be defined. And a HistoryQueryBuilder needs to be added to the package. The history query builder knows about the specific hibernate history model and provides convenience methods to build HQL queries very easily. > 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] 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: ------------------------------ Comment: was deleted > 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: ----------------------------------- in meeting with Guillaume we concluded the following a package org.jbpm.pvm.history will be created. it will have following main model classes: HistoryProcessInstance HistoryNode HistoryVariable the package will also contain a HistoryLogSession The history log session will have a map that maps process log classes to handlers. The handlers will be anonymous inner classes. For each incoming log, the HistoryLogSession will lookup the handler in the map and let it process the processlog. Processing the processlog means that the information will be integrated in the history model. In parallel with working out the model and the history log session, the queries need to be defined. And a HistoryQueryBuilder needs to be added to the package. > 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] Created: (JBPM-1428) review project dependencies

by Tom Baeyens (JIRA)

review project dependencies ---------------------------- Key: JBPM-1428 URL: https://jira.jboss.org/jira/browse/JBPM-1428 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens too much libs in the distribution. <optional>true</optional> can control that. see also http://maven.apache.org/guides/introduction/introduction-to-optional-and-... http://maven.apache.org/pom.html#Dependencies " # scope: This element refers to the classpath of the task at hand (compiling and runtime, testing, etc.) as well as how to limit the transitivity of a depedency. There are five scopes available: * compile - this is the default scope, used if none is specified. Compile dependencies are available in all classpaths. Furthermore, those dependencies are propagated to dependent projects. * provided - this is much like compile, but indicates you expect the JDK or a container to provide it at runtime. It is only available on the compilation and test classpath, and is not transitive. * runtime - this scope indicates that the dependency is not required for compilation, but is for execution. It is in the runtime and test classpaths, but not the compile classpath. * test - this scope indicates that the dependency is not required for normal use of the application, and is only available for the test compilation and execution phases. * system - this scope is similar to provided except that you have to provide the JAR which contains it explicitly. The artifact is always available and is not looked up in a repository. # optional: Marks optional a dependency when this project itself is a dependency. Confused? For example, imagine a project A that depends upon project B to compile a portion of code that may not be used at runtime, then we may have no need for project B for all project. So if project X adds project A as its own dependency, then Maven will not need to install project B at all. Symbolically, if => represents a required dependency, and --> represents optional, although A=>B may be the case when building A X=>A-->B would be the case when building X. In the shortest terms, optional lets other projects know that, when you use this project, you do not require this dependency in order to work correctly. " -- 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
1
0 / 0

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

by Tom Baeyens (JIRA)

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) Components: PVM Reporter: 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

16 years, 5 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2008