June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-834) Build fails on cvs head in console/src/main/java/org/jbpm/webapp/tag/jbpm/ui/DataTable.java

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-834?page=all ] Thomas Diesler resolved JBPM-834. --------------------------------- Resolution: Out of Date > Build fails on cvs head in console/src/main/java/org/jbpm/webapp/tag/jbpm/ui/DataTable.java > ------------------------------------------------------------------------------------------- > > Key: JBPM-834 > URL: http://jira.jboss.com/jira/browse/JBPM-834 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM jPDL 3.2 beta 2 > Environment: cvs head build, javac 1.5.0_9, XEmacs, ant. > Reporter: Chris Russell > Assigned To: Tom Baeyens > Priority: Trivial > > getChildren().add(element) must cast element to (UIComponent) > cvs diff of the fix to console/src/main/java/org/jbpm/webapp/tag/jbpm/ui/DataTable.java > diff -r1.2 DataTable.java > 158c158 > < final boolean result = comp.getChildren().add(element); > --- > > final boolean result = comp.getChildren().add((UIComponent)element); -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-723) Commit ws source into cvs

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-723?page=all ] Thomas Diesler resolved JBPM-723. --------------------------------- Resolution: Out of Date > Commit ws source into cvs > ------------------------- > > Key: JBPM-723 > URL: http://jira.jboss.com/jira/browse/JBPM-723 > Project: JBoss jBPM > Issue Type: Sub-task > Reporter: Ronald van Kuijk > Assigned To: Ronald van Kuijk > Priority: Minor > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-728) add jump to function

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-728?page=all ] Thomas Diesler resolved JBPM-728. --------------------------------- Resolution: Out of Date > add jump to function > -------------------- > > Key: JBPM-728 > URL: http://jira.jboss.com/jira/browse/JBPM-728 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > > Whenever a user wants to jump to a given node, setNode might not be sufficient. Token.setNode only works properly if you're in a wait state. If during process execution you want to jump to a given node, you currently have to wait till the process enters a wait state and do the setNode then. This can impose side effects. One way of doing this is by means of throwing an exception. Maybe jbpm can use an exception internally to implement the jump... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-729) Add jbossws1.0.x to the jbpm repository

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-729?page=all ] Thomas Diesler resolved JBPM-729. --------------------------------- Resolution: Out of Date > Add jbossws1.0.x to the jbpm repository > --------------------------------------- > > Key: JBPM-729 > URL: http://jira.jboss.com/jira/browse/JBPM-729 > Project: JBoss jBPM > Issue Type: Sub-task > Environment: N/A > Reporter: Ronald van Kuijk > Assigned To: Tom Baeyens > > Could you do this? currently I rely on the presence of a JBoss AS installation -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-726) Invalid DbPersistenceServiceFactory XML config example in Section 7.2.2 of documentation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-726?page=all ] Thomas Diesler resolved JBPM-726. --------------------------------- Resolution: Out of Date > Invalid DbPersistenceServiceFactory XML config example in Section 7.2.2 of documentation > ---------------------------------------------------------------------------------------- > > Key: JBPM-726 > URL: http://jira.jboss.com/jira/browse/JBPM-726 > Project: JBoss jBPM > Issue Type: Bug > Components: Documentation > Affects Versions: jBPM 3.1.2 > Reporter: Chris OBrien > Assigned To: Tom Baeyens > > After fighting with the configuration to disable jBPM's management of transactions, and digging through the code, I finally figured out the issue. An incorrect user guide. > In section 7.2.2. The DbPersistenceServiceFactory, it shows an XML snipped how to setup jBPM's persistence layer so it will not fuss with transactions. The example given is wrong. > Where it says bean factory="org.jbpm.persistence.db.DbPersistenceServiceFactory" > It should say bean class="org.jbpm.persistence.db.DbPersistenceServiceFactory" -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-724) create tests for jbpm WS frontend

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-724?page=all ] Thomas Diesler resolved JBPM-724. --------------------------------- Resolution: Out of Date > create tests for jbpm WS frontend > --------------------------------- > > Key: JBPM-724 > URL: http://jira.jboss.com/jira/browse/JBPM-724 > Project: JBoss jBPM > Issue Type: Sub-task > Reporter: Ronald van Kuijk > Assigned To: Ronald van Kuijk > Priority: Minor > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-750) NPE on TaskInstance.java on end() when TaskInstance created manually and no Task is assigned

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-750?page=all ] Thomas Diesler resolved JBPM-750. --------------------------------- Resolution: Out of Date > NPE on TaskInstance.java on end() when TaskInstance created manually and no Task is assigned > -------------------------------------------------------------------------------------------- > > Key: JBPM-750 > URL: http://jira.jboss.com/jira/browse/JBPM-750 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.2 > Environment: All > Reporter: Uhyon Chung > Assigned To: Tom Baeyens > > When you create a new TaskInstance manually (from a ActionHandler) without a Task assigned, an NPE occurs in a log statement in the end(Transition) method. > If you take a look at the end method, it seems to allow null tasks, because it checks whether the task is null before execution methods on the task field. However, in the log.debug statement, it does not do this null check, which causes an NPE. I'm not quite sure if having a TaskInstance without a Task is really a good practice, but otherwise I would need to create a Task object and add it to the ProcessDefinition, which is definitely not something I want to be doing since I just want to add a task instance to the user's task list dynamically. > I've created a small fix, and the patch is as follows.I made the patch based on the 3.1.2 on CVS using Eclipse patch. > ### Eclipse Workspace Patch 1.0 > #P jbpm3 > Index: jpdl/jar/src/main/java/org/jbpm/taskmgmt/exe/TaskInstance.java > =================================================================== > RCS file: /cvsroot/jbpm/jbpm.3/jpdl/jar/src/main/java/org/jbpm/taskmgmt/exe/TaskInstance.java,v > retrieving revision 1.6 > diff -u -r1.6 TaskInstance.java > --- jpdl/jar/src/main/java/org/jbpm/taskmgmt/exe/TaskInstance.java 8 Sep 2006 11:23:07 -0000 1.6 > +++ jpdl/jar/src/main/java/org/jbpm/taskmgmt/exe/TaskInstance.java 15 Sep 2006 06:27:07 -0000 > @@ > if (transition==null) { > - log.debug("completion of task '"+task.getName()+"' results in taking the default transition"); > + log.debug("completion of task '"+(task==null?getName():task.getName())+"' results in taking the default transition"); > token.signal(); > } else { > - log.debug("completion of task '"+task.getName()+"' results in taking transition '"+transition+"'"); > + log.debug("completion of task '"+(task==null?getName():task.getName())+"' results in taking transition '"+transition+"'"); > token.signal(transition); > } > } > -464,10 +464,10 @@ > ) { -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-693) Change ant build scripts in starter kit to make the JBoss HTTP port number as a property instead of hardcoded.

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-693?page=all ] Thomas Diesler resolved JBPM-693. --------------------------------- Resolution: Out of Date > Change ant build scripts in starter kit to make the JBoss HTTP port number as a property instead of hardcoded. > --------------------------------------------------------------------------------------------------------------- > > Key: JBPM-693 > URL: http://jira.jboss.com/jira/browse/JBPM-693 > Project: JBoss jBPM > Issue Type: Feature Request > Affects Versions: jBPM 3.1.1 > Environment: JBoss 4.0.4 > Reporter: Brad O'Hearne > Assigned To: Tom Baeyens > Priority: Minor > Original Estimate: 15 minutes > Remaining Estimate: 15 minutes > > This is a fairly trivial request, but make the port number of the JBoss installation a configuration property, rather than hardcoding it in the build.deploy.xml file. Its kind of a nuisance to have to change these manually on all the deploy targets. Thx. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-687) create setup for easy analytics development

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-687?page=all ] Thomas Diesler resolved JBPM-687. --------------------------------- Resolution: Out of Date > create setup for easy analytics development > ------------------------------------------- > > Key: JBPM-687 > URL: http://jira.jboss.com/jira/browse/JBPM-687 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Critical > > set up an environment where it is easy to run a hsqldb as a separate server process. > * include scripts to run hsqldb as a separate server process > * include scripts to create the JBPM db schema > * include data and scripts to upload the example identity data > * include processes and scripts to upload a few example processes > * include a few unit test cases that generate some logging data so that it is easy to start developing analytics queries > > then include instructions on how the hibernate tools can be used to connect to this db. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-715) Implement runtime automagically generated forms

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-715?page=all ] Thomas Diesler resolved JBPM-715. --------------------------------- Resolution: Out of Date > Implement runtime automagically generated forms > ----------------------------------------------- > > Key: JBPM-715 > URL: http://jira.jboss.com/jira/browse/JBPM-715 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Web Interface > Environment: n/a > Reporter: Ronald van Kuijk > Assigned To: Ronald van Kuijk > Priority: Minor > > As long as it is not possible to generate an .xhtml file from the gpd for a task, it should be possible to use a designed process without the need to create custom forms. > Initially this would be identical to the 3.1 automagical forms (not taking into account the variable type) but it should some day. > Taking the variable type into account would be possible if the variable already exists in the process instances, but if it is initially filled via a type agnostic ui, it will always be string. If it is set via the api, we could take it into account. -- 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, 6 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 June 2008