March 2010 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-2806) Identity API doesn't allow access to parent field in Group

by Michele Mauro (JIRA)

Identity API doesn't allow access to parent field in Group ---------------------------------------------------------- Key: JBPM-2806 URL: https://jira.jboss.org/jira/browse/JBPM-2806 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.3 Reporter: Michele Mauro The Identity API does not have a method to access the parent of a Group. org.jbpm.api.identity.Group has only getId(), getName() and getType() methods. Probably this will be resolved with the integration of JBossIDM, but if the integration is not going to make it for 4.4, this one should be easy to fix alone by itself, since the column seems to be mapped and is present in the db. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBPM-2714) fix hudson upgrade job

by Tom Baeyens (JIRA)

fix hudson upgrade job ---------------------- Key: JBPM-2714 URL: https://jira.jboss.org/jira/browse/JBPM-2714 Project: jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Tom Baeyens Assignee: Tom Baeyens Fix For: jBPM 4.4 we saw problems with it last iteration. analyse and fix those. also investigate if the test-upgrade project needs to be published for each release. http://repository.jboss.org/maven2/org/jbpm/jbpm4/jbpm-test-upgrade/ if so, make sure that is automatic in the future or added to the release guide. -- 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

2
9
0 / 0

[JBoss JIRA] Created: (JBPM-2627) Reporting on tomcat fails due to missing JNDI datasource configuration

by Heiko Braun (JIRA)

Reporting on tomcat fails due to missing JNDI datasource configuration ---------------------------------------------------------------------- Key: JBPM-2627 URL: https://jira.jboss.org/jira/browse/JBPM-2627 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Fix For: jBPM 4.2 Currently the report generation fails because there is no JBPM datasource configured in tomcat. Without the reports will be DB dependend and not work. In order to fix report generation on tomcat a proper JNDI datasource ('java:/JbpmDS') would need to be configured as described here: http://tomcat.apache.org/tomcat-6.0-doc/jndi-datasource-examples-howto.html -- 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
7
0 / 0

[JBoss JIRA] Created: (JBPM-2765) With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated

by Jan Scherf (JIRA)

With the introduction of the id generator sql-scripts (${jbpm.home}/install/src/db/create) were not updated ----------------------------------------------------------------------------------------------------------- Key: JBPM-2765 URL: https://jira.jboss.org/jira/browse/JBPM-2765 Project: jBPM Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jBPM 4.3 Environment: Databases HSQLDB, MySQL, Oracle, PostgrasSql: if database tables where created using the sql-scripts in ${jbpm.home}/install/src/db/create Reporter: Jan Scherf Fix For: jBPM 4.4 org.jbpm.pvm.internal.model.ExecutionImpl.save() crashs with database-error. reason: - DatabaseIdComposer.createId(...) produces datatype string - but sql-Skripts create dbid-colums whose datatype is integer __________________________________________________________________________________________ See more Details on: http://community.jboss.org/message/521822 The reason of this problem can be found in org.jbpm.pvm.internal.id.DatabaseIdComposer.createId(...) which is called in org.jbpm.pvm.internal.model.ExecutionImpl.save() to initialize ExecutionImpl.dbid. Property dbid is mapped to database table JBPM4_EXECUTION (see: jbpm.execution.hbm.xml). As you can see in sql-files in ${jbpm.home}/src/db/create, the database-field-datatype of property DBID_ is a kind of integer. But DatabaseIdComposer.createId(...) produces String ... It seems that with the introduction of the id generator these scripts were not updated. -- 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
12
0 / 0

[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-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-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 March 2010