June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-643) Change "load" methods to indicate when an entity is "not found"

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-643?page=all ] Thomas Diesler resolved JBPM-643. --------------------------------- Resolution: Out of Date > Change "load" methods to indicate when an entity is "not found" > --------------------------------------------------------------- > > Key: JBPM-643 > URL: http://jira.jboss.com/jira/browse/JBPM-643 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1 > Environment: All > Reporter: Jim Rigsbee > Assigned To: Tom Baeyens > Original Estimate: 1 week > Remaining Estimate: 1 week > > For example, context.getGraphSession( ).loadProcessInstance uses a hiberate session.load to retrieve the instance. This method does not indicate if the entity is not found in the database. Hibernate documentation suggests using the get( ) method instead. > We need to make sure that the user can tell when entity is not found. This applies to all of the entity loading in the core engine. -- 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-629) Db specific hibernate.properties not overriden when running jbpm.db tests.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-629?page=all ] Thomas Diesler resolved JBPM-629. --------------------------------- Resolution: Out of Date > Db specific hibernate.properties not overriden when running jbpm.db tests. > -------------------------------------------------------------------------- > > Key: JBPM-629 > URL: http://jira.jboss.com/jira/browse/JBPM-629 > Project: JBoss jBPM > Issue Type: Task > Reporter: Rajesh Rajasekaran > Assigned To: Tom Baeyens > > The documentation under jbpm.db/readme.html says > "Modify the hibernate.properties file in the folder for your database (e.g /postgresql/hibernate.properties) to suit your requirements. Add the correct connection user name, connection password and connection url for the driver. You can override any hibernate properties configured in jbpm.3/src/config.files/hibernate.cfg.xml within this properties file." > This behaviour does not happen. The tests when run with say "mysql.test" still uses the hsqldb specific jdbc properties from jbpm.3/src/config.files/hibernate.cfg.xml -- 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-655) node packaging and decoupling

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-655?page=all ] Thomas Diesler resolved JBPM-655. --------------------------------- Resolution: Out of Date > node packaging and decoupling > ----------------------------- > > Key: JBPM-655 > URL: http://jira.jboss.com/jira/browse/JBPM-655 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Koen Aers > > This task is to collect all the artifacts for implementing nodes in jBPM 4. > * Node implementation class > * XML parsing information > * Node persistence: > --- With a hibernate mapping file. In that case, we should scan all node packages somehow to find all the hibernate mapping files. Also this implies that it is not possible to have a common base schema for different languages such as jPDL and BPEL. > --- Persisting node-specific configuration information in descriptors. We can have a generic set of mappings for persisting descriptor information. If the node specific configuration information is parsed to descriptors, it will always be storable. In that case, we just need add the sub class mapping and the type identifier. > * Graphical information: > --- icon > --- form -- 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-657) simple automatic node process

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-657?page=all ] Thomas Diesler resolved JBPM-657. --------------------------------- Resolution: Out of Date > simple automatic node process > ----------------------------- > > Key: JBPM-657 > URL: http://jira.jboss.com/jira/browse/JBPM-657 > Project: JBoss jBPM > Issue Type: Sub-task > Components: Core Engine, Documentation > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > The first example should show a few automatic nodes. With automatic nodes, i mean nodes that have an action which does not result into a wait state. The idea is that the reader of this example should be able to see how a few pieces of java code are linked together into a process graph. Maybe a decision could be used as well. > The process should be defined in a separate processdefinition.xml file. > The tutorial should have a process file and a unit test. The unit test should have persistence. > A readme.html and a build.xml should accompany the tutorial example. The readme should explain what is shown in the example and the relevance. The fact that persistence is of limited use here (because there are no wait states) should be explained. > this example should NOT contain and process concurrency (forks and joins) and no more then 6 nodes (start and end states included). -- 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-573) enable expression language fetching of process variables for the current token

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-573?page=all ] Thomas Diesler resolved JBPM-573. --------------------------------- Resolution: Out of Date > enable expression language fetching of process variables for the current token > ------------------------------------------------------------------------------ > > Key: JBPM-573 > URL: http://jira.jboss.com/jira/browse/JBPM-573 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > -- 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-572) copy swimlane instances in sub-processes

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-572?page=all ] Thomas Diesler resolved JBPM-572. --------------------------------- Resolution: Out of Date > copy swimlane instances in sub-processes > ---------------------------------------- > > Key: JBPM-572 > URL: http://jira.jboss.com/jira/browse/JBPM-572 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > Now, a process-state is only able to copy variables from and to subprocesses. This feature request is to have the same support for swimlane instances. -- 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-559) Whitespace not ignored in transition's condition element

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-559?page=all ] Thomas Diesler resolved JBPM-559. --------------------------------- Resolution: Out of Date > Whitespace not ignored in transition's condition element > -------------------------------------------------------- > > Key: JBPM-559 > URL: http://jira.jboss.com/jira/browse/JBPM-559 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM 3.1 > Environment: Win XP, jBPM 3.1 in custom web app in JBoss 4.0.3 > Reporter: Ian Terrell > Assigned To: Tom Baeyens > Priority: Minor > > It appears that if whitespace is present at the beginning of a condition, the actual expression is either not evaluated or not evaluated properly; it always returns false. > Clarification: the problem exists with and without the use of <![CDATA[ ... ]]> -- 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-597) merge with the portal identity component

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-597?page=all ] Thomas Diesler resolved JBPM-597. --------------------------------- Resolution: Out of Date > merge with the portal identity component > ---------------------------------------- > > Key: JBPM-597 > URL: http://jira.jboss.com/jira/browse/JBPM-597 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > It would be great if we could merge that one with the jbpm identity component. > The first thing that needs to be done is to check out the portal identity component. We must examine what features are necessary, which of the two will be used to create the new identity module. -- 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-610) web service interface

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-610?page=all ] Thomas Diesler resolved JBPM-610. --------------------------------- Resolution: Out of Date > web service interface > --------------------- > > Key: JBPM-610 > URL: http://jira.jboss.com/jira/browse/JBPM-610 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > create a web service interface to the SLSB command based session facade -- 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

16 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-591) Priority for Tokens or Priority propagation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-591?page=all ] Thomas Diesler resolved JBPM-591. --------------------------------- Resolution: Out of Date > Priority for Tokens or Priority propagation > ------------------------------------------- > > Key: JBPM-591 > URL: http://jira.jboss.com/jira/browse/JBPM-591 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1 > Reporter: Alexey Kakunin > Assigned To: Tom Baeyens > > For current moment priority may be specified for Task (and as result will be assigned to TaskInstance). > User may change priority of task instance... but... I think it is not enough. > For example - we have process for processing ToDos. This process has different steps: specifying todo, assignment, processing, requesting additionalo information, results verification... > We cannot say in process definition priority for this tasks - usually it is normal. > But - it is much more improtant to be able to specify priority for the process instance - so, then we create new todo (and stating new process instance with new token) - specify priority of this process. > Here I see different ways to implement it: > * Priority Propagation - priority assigned to the task instance stored in token and then assigned to the all next tasks (in case then no any special priority is not specified in this task); > * Priority may be assigned to the process (in this case we will have process priority - and priority of the task in this process); > * Priority may be assigned to the token (and in split node we can assig different priorities to different subtokens); > Of course it is possible implement by ourself by writting special actors and so on - thanks to the really high jBPM flexibility, but I think it is good feature for jBPM core -- 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

16 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2008