July 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2482) console should pass authenticated user to engine operations

by Tom Baeyens (JIRA)

console should pass authenticated user to engine operations ----------------------------------------------------------- Key: JBPM-2482 URL: https://jira.jboss.org/jira/browse/JBPM-2482 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Tom Baeyens Assignee: Joram Barrez Fix For: jBPM 4.2 following pieces of console code should be revisisted so that the authenticated user is passed to the engine operations: public ProcessInstanceRef newInstance(String definitionId, Map<String, Object> processVars) { Environment env = ((EnvironmentFactory)processEngine).openEnvironment(); try { ExecutionService execService = this.processEngine.getExecutionService(); Execution exec = execService.startProcessInstanceById(definitionId); execService.setVariables(exec.getId(), processVars); return ModelAdaptor.adoptExecution((ExecutionImpl)exec); } finally{ env.close(); } } First, the API needs to expose a way on how to set the authenticated user programmatically. -- 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 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2770) Provide way to signal execution in state with timer

by Nils Preusker (JIRA)

Provide way to signal execution in state with timer --------------------------------------------------- Key: JBPM-2770 URL: https://jira.jboss.org/jira/browse/JBPM-2770 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.x Environment: Not specific to environment Reporter: Nils Preusker It would be useful to be able to either signal an execution that is in a wait state with a timer attached to it, or cancel a timer and the attached job and then signal the execution. For a more detailed description, consider the attached test case and process definition and have a look at the referenced forum post. -- 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 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-2904) allow slash in jpdl activity name

by Huisheng Xu (JIRA)

allow slash in jpdl activity name --------------------------------- Key: JBPM-2904 URL: https://jira.jboss.org/browse/JBPM-2904 Project: jBPM Issue Type: Patch Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.3 Reporter: Huisheng Xu Assignee: Huisheng Xu Priority: Optional Fix For: jBPM 4.4 Provide a parameter 'jbpm.activity.allow.slash' in jbpm.cfg.xml to decision whether we should validate the activity name for whether or not allow contains slash(/). Default is false, not allow slash(/) in activity name. If someone want to use slash(/) in activity name, should set <true name='jbpm.activity.allow.slash'/> in <process-engine-context>. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

3
13
0 / 0

[JBoss JIRA] Created: (JBPM-2912) update structure of documentation project

by David Le Sage (JIRA)

update structure of documentation project ----------------------------------------- Key: JBPM-2912 URL: https://jira.jboss.org/browse/JBPM-2912 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM 3.2.8 Reporter: David Le Sage Assignee: David Le Sage Fix For: jBPM 3.2.10 We need to update the structure of the jBPM 3 docs so the docbook is consumable in both jDocBook and Publican. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPM-2910) Unescaped text in documentation - dev guide - ch17-SpringIntegration.xml

by Jonathan Chard (JIRA)

Unescaped text in documentation - dev guide - ch17-SpringIntegration.xml ------------------------------------------------------------------------ Key: JBPM-2910 URL: https://jira.jboss.org/browse/JBPM-2910 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: jBPM 4.3 Reporter: Jonathan Chard In the file ch17-SpringIntegration.xml there is a block of text that shows you how to set up the Spring helper. (lines 86-90) The xml is not escaped, so the text is not included in the generated documentation. This text is quite useful! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-1453) merge job notification booleans

by Tom Baeyens (JIRA)

merge job notification booleans ------------------------------- Key: JBPM-1453 URL: https://jira.jboss.org/jira/browse/JBPM-1453 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: PVM Reporter: Tom Baeyens Priority: Critical merge the 2 independent booleans that keep track whether a notification to the job executor was already sent JobExecutorMessageSession.isNotificationAdded and JobExecutorTimerSession.jobExecutorNotificationScheduled -- 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 months

3
16
0 / 0

[JBoss JIRA] Created: (JBPM-2427) Look at if need to add the optional "language" attribute to mail activitly

by Jim Ma (JIRA)

Look at if need to add the optional "language" attribute to mail activitly -------------------------------------------------------------------------- Key: JBPM-2427 URL: https://jira.jboss.org/jira/browse/JBPM-2427 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0 Reporter: Jim Ma There is no "language" attribute in jpdl-4.0.xsd. look it if we need to add it as optional. -- 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 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPM-2515) End activityname not accessible through History API

by Joram Barrez (JIRA)

End activityname not accessible through History API --------------------------------------------------- Key: JBPM-2515 URL: https://jira.jboss.org/jira/browse/JBPM-2515 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: jBPM 4.0, jBPM 4.1 Reporter: Joram Barrez Priority: Minor See forum reference. There is no operation to retrieve the end activity name through the history API, altough the String is stored in the HistoryProcessInstanceImpl class. -- 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 months

4
10
0 / 0

[JBoss JIRA] Created: (JBPM-2553) Violation of unique constratin with two splits

by David Loiseau (JIRA)

Violation of unique constratin with two splits ---------------------------------------------- Key: JBPM-2553 URL: https://jira.jboss.org/jira/browse/JBPM-2553 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.1 Reporter: David Loiseau Thow split steps with two identical transition names cause a violation of unique constraint in JBPM4_EXECUTION table. Process Definition: <?xml version="1.0" encoding="UTF-8"?> <process key="test" name="test" xmlns="http://jbpm.org/4.0/jpdl"> <start g="82,38,41,27" name="start1"> <transition g="-43,-18" name="to fork1" to="fork1"/> </start> <fork g="79,112,25,20" name="fork1"> <transition name="to task1" to="task1" g="-44,-18"/> <transition name="to task2" to="task2" g="-44,-18"/> </fork> <fork g="88,263,65,27" name="fork2"> <transition name="to task1" to="task4" g="-44,-18"/> <transition name="to task3" to="task3" g="-44,-18"/> </fork> <task assignee="test" name="task1" g="75,189,60,42"> <transition name="to fork2" to="fork2" g="-43,-18"/> </task> <task name="task2" g="163,117,61,31"/> <task name="task3" g="189,268,59,37"/> <task name="task4" g="93,340,52,40"/> </process> Test code: ProcessEngine processEngine = Configuration.getProcessEngine(); RepositoryService repositoryService = (RepositoryService) processEngine.get(RepositoryService.class); String deploymentId = repositoryService .createDeployment() .addResourceFromClasspath("test.jpdl.xml") .deploy(); Execution execution = processEngine.getExecutionService().startProcessInstanceByKey("test"); Task task = (Task)processEngine.getTaskService().findPersonalTasks("test").get(0); processEngine.getTaskService().completeTask(task.getId(),"to fork2"); Exception: Caused by: java.sql.SQLException: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_CT_970 in statement [update JBPM4_EXECUTION set DBVERSION_=?, ACTIVITYNAME_=?, PROCDEFID_=?, HASVARS_=?, NAME_=?, KEY_=?, ID_=?, STATE_=?, SUSPHISTSTATE_=?, PRIORITY_=?, HISACTINST_=?, PARENT_=?, INSTANCE_=?, SUPEREXEC_=?, SUBPROCINST_=? where DBID_=? and DBVERSION_=?] at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.executeUpdate(Unknown Source) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2435) ... 39 more -- 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 months

4
11
0 / 0

[JBoss JIRA] Created: (JBPM-2614) TimerSessionBinding does not allow 3rd party TimerSession implementations

by sdfsd sdfsd (JIRA)

TimerSessionBinding does not allow 3rd party TimerSession implementations ------------------------------------------------------------------------- Key: JBPM-2614 URL: https://jira.jboss.org/jira/browse/JBPM-2614 Project: jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Runtime Engine Affects Versions: jBPM 4.x Reporter: sdfsd sdfsd We want to use our own scheduler for Timers but even if the infrastracture is in place one can not configure it's own implementation of TimerSession. The <timer-session/> element allows only target ='ejb' and nothing else will be parsed by the method TimerSessionBinding.parse(). I can't understand why can't I provide my own implementation of TimerSession. the Solution would be to change add and attribute className to <timer-session/> element and to change the TimerSessionBinding.parse() method like this : objectDescriptor.setClassName(XmlUtil.attribute(element, "class")); you can also add a target like 'custom' and only then check the 'class' attribute. Something like this: public Object parse(Element element, Parse parse, Parser parser) { ObjectDescriptor objectDescriptor = new ObjectDescriptor(); String target = XmlUtil.attribute(element, "target"); if ((target!=null){ if ("ejb".equalsIgnoreCase(target))) { objectDescriptor.setClassName("org.jbpm.enterprise.internal.ejb.EnterpriseTimerSession"); } else if ("custom".equalsIgnoreCase(target))) { objectDescriptor.setClassName(XmlUtil.attribute(element, "class")); } } else { // wire the JobExecutorTimerSession objectDescriptor.setClassName(JobExecutorTimerSession.class.getName()); // inject fields objectDescriptor.addInjection("transaction", new TransactionRefDescriptor()); objectDescriptor.addInjection("jobExecutor", new EnvDescriptor(JobExecutor.class)); objectDescriptor.addInjection("session", new ContextTypeRefDescriptor(Session.class)); } return objectDescriptor; } -- 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 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues July 2010