[JBoss JIRA] Assigned: (JBPM-602) create submit button component for task forms
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-602?page=all ]
Ronald van Kuijk reassigned JBPM-602:
-------------------------------------
Assignee: Ronald van Kuijk (was: Tom Baeyens)
> create submit button component for task forms
> ---------------------------------------------
>
> Key: JBPM-602
> URL: http://jira.jboss.com/jira/browse/JBPM-602
> Project: JBoss jBPM
> Issue Type: Task
> Components: Web Interface
> Reporter: Tom Baeyens
> Assigned To: Ronald van Kuijk
>
> 3 ui components should be created for the 3 type of buttons in a taskform: save, saveAndClose and cancel
> The saveAndClose component should be created as a shortcut for
> <input type="submit" jsfc="h:commandButton" id="transitionButton" action="#{taskBean.saveAndClose}" value="OK" onclick="document.forms['taskform'].elements['taskform:transitionName'].value='OK'"/>
> This component should work in combination with the form component
> transitionName and label should be the parameters of the button component.
> The 'save' component should only have the label parameter.
> The cancel component should not have any parameters at all.
> For examples on ui components, see package org.jbpm.webapp.ui and WEB-INF/jbpm.taglib.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
19 years, 12 months
[JBoss JIRA] Closed: (JBPM-623) DatabaseServerLoginModule in login-config.xml does not work with oracle
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-623?page=all ]
Ronald van Kuijk closed JBPM-623.
---------------------------------
checked (or should QA do this???)
> DatabaseServerLoginModule in login-config.xml does not work with oracle
> -----------------------------------------------------------------------
>
> Key: JBPM-623
> URL: http://jira.jboss.com/jira/browse/JBPM-623
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Web Interface
> Affects Versions: jBPM 3.2 alpha 1
> Environment: linux kernel 2.6.xx, sun jdk 1.5.0_06, jboss 4.0.3sp1, cvs head from 04/04/06
> Reporter: Ronald van Kuijk
> Assigned To: Tom Baeyens
> Priority: Minor
>
> The select statement for the rolesQuery does not work on oracle, at least not on 'Oracle9i Enterprise Edition Release 9.2.0.5.0 - Production' with the 9 or 10 drivers.
> The error I get is that the command is not properly ended:
> Error Code: 933, SQL State: 42000] ORA-00933: SQL command not properly ended
> removing the 'as' statements in the select solves the problem, so
> SELECT g.NAME_ ,'Roles'
> FROM JBPM_ID_USER as u,
> JBPM_ID_MEMBERSHIP as m,
> JBPM_ID_GROUP as g
> WHERE g.TYPE_='security-role'
> AND m.GROUP_ = g.ID_
> AND m.USER_ = u.ID_
> AND u.NAME_=?
> does not work, but
> SELECT g.NAME_ ,'Roles'
> FROM JBPM_ID_USER u,
> JBPM_ID_MEMBERSHIP m,
> JBPM_ID_GROUP g
> WHERE g.TYPE_='security-role'
> AND m.GROUP_ = g.ID_
> AND m.USER_ = u.ID_
> AND u.NAME_=?
> does....
> my sql knowledge is very, very little, so do not ask me to seek out why one is working and the other isn't.
--
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
19 years, 12 months
[JBoss JIRA] Resolved: (JBPM-623) DatabaseServerLoginModule in login-config.xml does not work with oracle
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-623?page=all ]
Ronald van Kuijk resolved JBPM-623.
-----------------------------------
Resolution: Done
Seems to work in 3.2 head....
> DatabaseServerLoginModule in login-config.xml does not work with oracle
> -----------------------------------------------------------------------
>
> Key: JBPM-623
> URL: http://jira.jboss.com/jira/browse/JBPM-623
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Web Interface
> Affects Versions: jBPM 3.2 alpha 1
> Environment: linux kernel 2.6.xx, sun jdk 1.5.0_06, jboss 4.0.3sp1, cvs head from 04/04/06
> Reporter: Ronald van Kuijk
> Assigned To: Tom Baeyens
> Priority: Minor
>
> The select statement for the rolesQuery does not work on oracle, at least not on 'Oracle9i Enterprise Edition Release 9.2.0.5.0 - Production' with the 9 or 10 drivers.
> The error I get is that the command is not properly ended:
> Error Code: 933, SQL State: 42000] ORA-00933: SQL command not properly ended
> removing the 'as' statements in the select solves the problem, so
> SELECT g.NAME_ ,'Roles'
> FROM JBPM_ID_USER as u,
> JBPM_ID_MEMBERSHIP as m,
> JBPM_ID_GROUP as g
> WHERE g.TYPE_='security-role'
> AND m.GROUP_ = g.ID_
> AND m.USER_ = u.ID_
> AND u.NAME_=?
> does not work, but
> SELECT g.NAME_ ,'Roles'
> FROM JBPM_ID_USER u,
> JBPM_ID_MEMBERSHIP m,
> JBPM_ID_GROUP g
> WHERE g.TYPE_='security-role'
> AND m.GROUP_ = g.ID_
> AND m.USER_ = u.ID_
> AND u.NAME_=?
> does....
> my sql knowledge is very, very little, so do not ask me to seek out why one is working and the other isn't.
--
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
19 years, 12 months
[JBoss JIRA] Resolved: (JBPM-590) Active tasks after process termination
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-590?page=all ]
Ronald van Kuijk resolved JBPM-590.
-----------------------------------
Resolution: Duplicate Issue
> Active tasks after process termination
> --------------------------------------
>
> Key: JBPM-590
> URL: http://jira.jboss.com/jira/browse/JBPM-590
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.1
> Environment: Win XP SP2
> Reporter: Alexey Kakunin
> Assigned To: Tom Baeyens
>
> I found that after terminating process with method ProcessInstance::end() there are still task assigned to the users.
> Here is simple TestCase for demonstating (I just change little bit org.jbpm.taskmgmt.exe.TaskAssignmentDBTest):
> package com.sample;
> import java.util.Arrays;
> import java.util.HashSet;
> import java.util.Iterator;
> import java.util.List;
> import java.util.Set;
> import org.jbpm.JbpmConfiguration;
> import org.jbpm.JbpmContext;
> import org.jbpm.db.AbstractDbTestCase;
> import org.jbpm.graph.def.ProcessDefinition;
> import org.jbpm.graph.exe.ExecutionContext;
> import org.jbpm.graph.exe.ProcessInstance;
> import org.jbpm.taskmgmt.def.AssignmentHandler;
> import org.jbpm.taskmgmt.exe.Assignable;
> import org.jbpm.taskmgmt.exe.TaskInstance;
> import junit.framework.TestCase;
> public class ProcessTerminationTestCase extends AbstractDbTestCase {
> public static class JohnAssignmentHandler implements AssignmentHandler {
> private static final long serialVersionUID = 1L;
> public void assign(Assignable assignable, ExecutionContext executionContext) throws Exception {
> assignable.setActorId("john");
> }
> }
>
> public void testPersonalTasklist() {
> ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(
> "<process-definition>" +
> " <start-state>" +
> " <transition to='work' />" +
> " </start-state>" +
> " <task-node name='work'>" +
> " <task name='feed the chickens'>" +
> " <assignment class='com.sample.ProcessTerminationTestCase$JohnAssignmentHandler' />" +
> " </task>" +
> " <task name='walk the dog'>" +
> " <assignment class='com.sample.ProcessTerminationTestCase$JohnAssignmentHandler' />" +
> " </task>" +
> " <task name='play with wife'>" +
> " <assignment class='com.sample.ProcessTerminationTestCase$JohnAssignmentHandler' />" +
> " </task>" +
> " </task-node>" +
> "</process-definition>"
> );
> graphSession.saveProcessDefinition(processDefinition);
>
> ProcessInstance processInstance = new ProcessInstance(processDefinition);
> processInstance.signal();
> jbpmContext.save(processInstance);
>
> newTransaction();
>
> List taskInstances = taskMgmtSession.findTaskInstances("john");
> assertNotNull(taskInstances);
> assertEquals(3, taskInstances.size());
>
> // now, terminate the process
> processInstance.end();
>
> //check that process was ended
> assertTrue("Process should be ended",
> processInstance.hasEnded());
>
> // so, people should have no any tasks related to this process
> taskInstances = taskMgmtSession.findTaskInstances("john");
> assertNotNull(taskInstances);
> assertEquals("John should have no tasks in finished process",
> 0,
> taskInstances.size());
> }
> }
> As we will see from test execution - after termination of the process John still has 3 opened task - that is not very correct
--
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
19 years, 12 months
[JBoss JIRA] Closed: (JBPM-590) Active tasks after process termination
by Ronald van Kuijk (JIRA)
[ http://jira.jboss.com/jira/browse/JBPM-590?page=all ]
Ronald van Kuijk closed JBPM-590.
---------------------------------
duplicate of JBPM-392
> Active tasks after process termination
> --------------------------------------
>
> Key: JBPM-590
> URL: http://jira.jboss.com/jira/browse/JBPM-590
> Project: JBoss jBPM
> Issue Type: Bug
> Components: Core Engine
> Affects Versions: jBPM 3.1
> Environment: Win XP SP2
> Reporter: Alexey Kakunin
> Assigned To: Tom Baeyens
>
> I found that after terminating process with method ProcessInstance::end() there are still task assigned to the users.
> Here is simple TestCase for demonstating (I just change little bit org.jbpm.taskmgmt.exe.TaskAssignmentDBTest):
> package com.sample;
> import java.util.Arrays;
> import java.util.HashSet;
> import java.util.Iterator;
> import java.util.List;
> import java.util.Set;
> import org.jbpm.JbpmConfiguration;
> import org.jbpm.JbpmContext;
> import org.jbpm.db.AbstractDbTestCase;
> import org.jbpm.graph.def.ProcessDefinition;
> import org.jbpm.graph.exe.ExecutionContext;
> import org.jbpm.graph.exe.ProcessInstance;
> import org.jbpm.taskmgmt.def.AssignmentHandler;
> import org.jbpm.taskmgmt.exe.Assignable;
> import org.jbpm.taskmgmt.exe.TaskInstance;
> import junit.framework.TestCase;
> public class ProcessTerminationTestCase extends AbstractDbTestCase {
> public static class JohnAssignmentHandler implements AssignmentHandler {
> private static final long serialVersionUID = 1L;
> public void assign(Assignable assignable, ExecutionContext executionContext) throws Exception {
> assignable.setActorId("john");
> }
> }
>
> public void testPersonalTasklist() {
> ProcessDefinition processDefinition = ProcessDefinition.parseXmlString(
> "<process-definition>" +
> " <start-state>" +
> " <transition to='work' />" +
> " </start-state>" +
> " <task-node name='work'>" +
> " <task name='feed the chickens'>" +
> " <assignment class='com.sample.ProcessTerminationTestCase$JohnAssignmentHandler' />" +
> " </task>" +
> " <task name='walk the dog'>" +
> " <assignment class='com.sample.ProcessTerminationTestCase$JohnAssignmentHandler' />" +
> " </task>" +
> " <task name='play with wife'>" +
> " <assignment class='com.sample.ProcessTerminationTestCase$JohnAssignmentHandler' />" +
> " </task>" +
> " </task-node>" +
> "</process-definition>"
> );
> graphSession.saveProcessDefinition(processDefinition);
>
> ProcessInstance processInstance = new ProcessInstance(processDefinition);
> processInstance.signal();
> jbpmContext.save(processInstance);
>
> newTransaction();
>
> List taskInstances = taskMgmtSession.findTaskInstances("john");
> assertNotNull(taskInstances);
> assertEquals(3, taskInstances.size());
>
> // now, terminate the process
> processInstance.end();
>
> //check that process was ended
> assertTrue("Process should be ended",
> processInstance.hasEnded());
>
> // so, people should have no any tasks related to this process
> taskInstances = taskMgmtSession.findTaskInstances("john");
> assertNotNull(taskInstances);
> assertEquals("John should have no tasks in finished process",
> 0,
> taskInstances.size());
> }
> }
> As we will see from test execution - after termination of the process John still has 3 opened task - that is not very correct
--
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
19 years, 12 months