December 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2505) ProcessInstanceQuery - no way to search by process variables

by Joao Fonseca (JIRA)

ProcessInstanceQuery - no way to search by process variables ------------------------------------------------------------ Key: JBPM-2505 URL: https://jira.jboss.org/jira/browse/JBPM-2505 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0.0 Alpha1, jBPM 4.0.0 Alpha2, jBPM 4.0.0.Beta1, jBPM 4.0.0.Beta2, jBPM 4.0.CR1, jBPM 4.0, jBPM 4.x, jBPM 4.2, jBPM 4.1 Reporter: Joao Fonseca Currently, there's no way of searching for process instances that contain variables set to a given value. Sometimes, there's no way of assigning a process instance key when starting a process, so we need to search for processes using values stored in some of the variables... -- 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

13 years, 11 months

8
13
0 / 0

[JBoss JIRA] Created: (JBPM-2687) Document how to install the web-console with a newbie tutorial under jboss, tomcat notably

by Alexandre Navarro (JIRA)

Document how to install the web-console with a newbie tutorial under jboss, tomcat notably ------------------------------------------------------------------------------------------ Key: JBPM-2687 URL: https://jira.jboss.org/jira/browse/JBPM-2687 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Affects Versions: jBPM 4.2 Reporter: Alexandre Navarro Fix For: GWT Console 1.0.x Document how to install the web-console with a newbie tutorial under jboss, tomcat notably. I tried to install it during 3 hours and at the end, it does not work and I gave up. It is very frustated not to have a good documentation to install webconsole on jboss, tomcat or some others appservers. -- 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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-1924) Improved participant UI

by Thomas Diesler (JIRA)

Improved participant UI ----------------------- Key: JBPM-1924 URL: https://jira.jboss.org/jira/browse/JBPM-1924 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Console Reporter: Thomas Diesler Priority: Critical * Participant UI: A production-ready inbox & task-form display solution, with a full-set of form controls, editable CSS, etc. Two Goldman CTOs felt this was the absolute highest priority to resolve ASAP (I received the same feedback from them in August). They have already made attempts to modify the current Admin Console (JSF/Gravel-based) and intend to tweak the GWT-based console. However, the Eclipse-tooling Visual Task Form Designer is relatively weak, it doesn't allow me to easily express things like Drop-Down list, numeric input only, check-box, pop-up calendar for date, etc. This UI is a process participants (e.g. clerk in the office) primary UI, their view of the world, they see all their own and their team's tasks (note: the current console shows all tasks for everybody, not just the logged in user). The current UI only uses inputText (single-line edits). The JBoss logo needs to be customizable (I want it to say Goldman in that upper left corner) I'll attempt to mark up some changes to the current console so you get a feel for their specific feedback. It should be noted that Amentra also felt this was a mandatory feature before we can call ourselves a BPM product. No Java Coding, just pointing & clicking. -- 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

13 years, 11 months

6
10
0 / 0

[JBoss JIRA] Created: (JBPM-2141) Use same deployment archive suffixes across target containers

by Heiko Braun (JIRA)

Use same deployment archive suffixes across target containers ------------------------------------------------------------- Key: JBPM-2141 URL: https://jira.jboss.org/jira/browse/JBPM-2141 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Integration Reporter: Heiko Braun Assignee: Heiko Braun In AS 5.0.0 we need to use the .jar suffix for deployments. This should become the same as in AS 4.2.x, when moving to 5.0.1 -- 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

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPM-2133) Error handling in CommandServiceBean.execute

by Volker Börchers (JIRA)

Error handling in CommandServiceBean.execute -------------------------------------------- Key: JBPM-2133 URL: https://jira.jboss.org/jira/browse/JBPM-2133 Project: JBoss jBPM Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.6.SP1 Environment: irrelevant Reporter: Volker Börchers Priority: Minor regards CommndServiceBean.execute(Command command): public Object execute(Command command) { JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); try { log.debug("executing " + command); return command.execute(jbpmContext); } catch (RuntimeException e) { sessionContext.setRollbackOnly(); throw e; } catch (Exception e) { sessionContext.setRollbackOnly(); throw new JbpmException("failed to execute " + command, e); } finally { jbpmContext.close(); } } If an exception occurres in Command.excute() it's important that this exception is propagated to the client to allow for proper exception handling to differentiate e.g. between a concurrency issue ("job is locked by...") and a database error. These exceptions are not propagated to the client if the jbpmContext.close() in the finally block throws an exceptions. This might very well happen since it performs non-trivial operations, e.g. access the database. (Actually it it seems to me as if the failure of jbpmContext.close() always happen, maybe since after the setRollbackOnly() no new connections are possible.) The following change will fix the problem: public Object execute(Command command) { JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); boolean exceptionThrown = false; try { log.debug("executing " + command); return command.execute(jbpmContext); } catch (RuntimeException e) { sessionContext.setRollbackOnly(); exceptionThrown = true; throw e; } catch (Exception e) { sessionContext.setRollbackOnly(); exceptionThrown = true; throw new JbpmException("failed to execute " + command, e); } finally { try { jbpmContext.close(); } catch (Exception e2) { if (exceptionThrown) { // JIRA XX: do not hide thrown exception log.error("exception on context close", e2); } else { throw e2; } } } } -- 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

14 years

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2142) No save of processInstance in TaskInstanceEndCommand

by Joram Barrez (JIRA)

No save of processInstance in TaskInstanceEndCommand ----------------------------------------------------- Key: JBPM-2142 URL: https://jira.jboss.org/jira/browse/JBPM-2142 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA, jBPM 3.2.7 GA Reporter: Joram Barrez Priority: Minor The TaskInstanceEndCommand does not save the processInstance. This means (among others) that the process logs will not be persisted to the database, since they are only stored upon a call to the save() method on the jBPM Context. The solution is simple, add jbpmContext.save(taskInstance.getProcessInstance()); to the command. I haven't checked the other commands, but the bug can occur in other commands. -- 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

14 years

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-2031) Some bidirectional associations do not use inverse="true"

by Tomasz Wysocki (JIRA)

Some bidirectional associations do not use inverse="true" --------------------------------------------------------- Key: JBPM-2031 URL: https://jira.jboss.org/jira/browse/JBPM-2031 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Engine Affects Versions: jBPM 3.3.1 GA Environment: Tested with MySQL with query log enabled in JUnit. Reporter: Tomasz Wysocki Priority: Minor Currently couple of bidirectional associations do not use inverse="true" on one-to-many side (collection) The examples are - ProcessInstance.instances - CompositeLog.children I'm sure there are more of them. Lack of inverse="true" results in additional "UPDATE" statement being issued by hibernate to create a relationship from a one-to-many side. This is not necessary when java code is updating both ends of an association. Some use-cases where lots of new processes are being created would see a performance improvement. CompositeLog logging overhead will decrease (only INSERT will be issued - no UPDATE) Please consider reviewing all of your bidirectional associations with respect to this optimization. -- 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

14 years

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-1463) task condition element is not exist jpdl3.2.3 schema, but in code

by xiong cf (JIRA)

task condition element is not exist jpdl3.2.3 schema, but in code ----------------------------------------------------------------- Key: JBPM-1463 URL: https://jira.jboss.org/jira/browse/JBPM-1463 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: jPDL 3 Affects Versions: jPDL 3.2.3 Reporter: xiong cf in jpdl-3.2.xsd : <xs:element name="task"> <xs:complexType> <xs:choice minOccurs="0" maxOccurs="unbounded"> <xs:element ref="description" /> <xs:element ref="assignment"/> <xs:element ref="controller"/> <xs:element ref="event"/> <xs:element ref="timer"/> <xs:element name="reminder"> <xs:complexType> <xs:attribute name="duedate" type="xs:string" use="required" /> <xs:attribute name="repeat" type="xs:string" /> </xs:complexType> </xs:element> </xs:choice> <xs:attribute name="name" type="xs:string" /> <xs:attribute name="blocking" type="booleanType" default="false"/> <xs:attribute name="signalling" type="booleanType" default="true"/> <xs:attribute name="description" type="xs:string" /> <xs:attribute name="duedate" type="xs:string" /> <xs:attribute name="swimlane" type="xs:string" /> <xs:attribute name="priority" type="priorityType" default="normal" /> <xs:attribute name="notify" type="booleanType" default="false"/> </xs:complexType> </xs:element> is not exist element condition. but in org.jbpm.jpdl.xml.JpdlXmlReader line312 has: // get the condition String condition = taskElement.elementTextTrim("condition"); if (condition!=null) { task.setCondition(condition); } else { task.setCondition(taskElement.attributeValue("condition")); } and in org.jbpm.graph.node.TaskNode line161 has: if ( (createTasks) && (tasks!=null) ) { Iterator iter = tasks.iterator(); while (iter.hasNext()) { Task task = (Task) iter.next(); executionContext.setTask(task); if (evaluateTaskCondition(task.getCondition(), executionContext)) { tmi.createTaskInstance(task, executionContext); } } } I think in jbpm3.2.3 should be spport task condition element , but document and schema not new -- 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

14 years

5
7
0 / 0

[JBoss JIRA] Created: (JBPM-2084) Changing variable to null in subprocess doesn't change variable in superprocess, even when acces is "WRITE"

by s p (JIRA)

Changing variable to null in subprocess doesn't change variable in superprocess, even when acces is "WRITE" ----------------------------------------------------------------------------------------------------------- Key: JBPM-2084 URL: https://jira.jboss.org/jira/browse/JBPM-2084 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.x Environment: windows XP/ java1.6/jboss 4.2.3GA/jbpm 3.2.7-SNAPSHOT from jboss svn Reporter: s p Superprocess A sets variable V to value "foo". Superprocess A calls subprocess B (A passes variable V to B with acces READ and WRITE). Subprocess B sets variable V to #{null}. Subprocess B finishes. Superprocess checks value of V - it is equal "foo". Expected behaviour: value of V equal #{null} in superprocess A after execution of subprocess B. This is becouse in ProcessState.java in methods execute and leave there is check: if (value!=null) { -- 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

14 years

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-2089) Whitepaper link is dead https://www.jboss.com/pdf/jbpm_whitepaper.pdf

by Anders Biehl Norgaard (JIRA)

Whitepaper link is dead https://www.jboss.com/pdf/jbpm_whitepaper.pdf --------------------------------------------------------------------- Key: JBPM-2089 URL: https://jira.jboss.org/jira/browse/JBPM-2089 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Environment: Firefox, Ubuntu 8.10 Reporter: Anders Biehl Norgaard https://www.jboss.com/pdf/jbpm_whitepaper.pdf which is a prominent link on https://www.jboss.com/products/jbpm/ gives a 404 -- 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

14 years

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues December 2009