May 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1170) Multiple Timers with same name on Node end prematurely

by David Roberts (JIRA)

Multiple Timers with same name on Node end prematurely ------------------------------------------------------ Key: JBPM-1170 URL: http://jira.jboss.com/jira/browse/JBPM-1170 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Environment: Jbpm 3.2.2, Tomcat 5.028, MySQL 5.0 Reporter: David Roberts Assigned To: Tom Baeyens When you have multiple Tasks on a Node, and each task has a Timer called, for example, "Reminder". Lets say each timer is set to repeat every 24 hours. If you complete one of the Tasks on the node, the Timer called "Reminder" on that task instance ends, but so does every other timer for all other tasks on that node with the name "Reminder". Surely this should not happen? You could avoid this by naming each Timer differenty, example "Reminder 1", "Reminder 2". But the problem may still happen if you have multiple task instances of the SAME task. Then the name of the Reminders will still be the same, so they will all end when completing one of the task instances. -- 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

14 years

4
4
0 / 0

[JBoss JIRA] Created: (JBPM-1166) fix SEAM timer transaction integration

by Tom Baeyens (JIRA)

fix SEAM timer transaction integration -------------------------------------- Key: JBPM-1166 URL: http://jira.jboss.com/jira/browse/JBPM-1166 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Reporter: Tom Baeyens Assigned To: Tom Baeyens -- 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

14 years

4
19
0 / 0

[JBoss JIRA] Created: (JBPM-1140) Empty <handler> element in <decision> cause org.jbpm.graph.def.DelegationException

by Rafa? ?ukowski (JIRA)

Empty <handler> element in <decision> cause org.jbpm.graph.def.DelegationException ---------------------------------------------------------------------------------- Key: JBPM-1140 URL: http://jira.jboss.com/jira/browse/JBPM-1140 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Rafa? ?ukowski Assigned To: Tom Baeyens Priority: Trivial That is my first issue, forgive me any mistakes and possible redundancy or duplication;) Using graphical designer I've created process file with empty <handler> : <decision name="decision1"> <handler></handler> <transition to="optional" name="to optional"></transition><transition to="first" name="to optional"></transition> </decision> And this is not working (org.jbpm.graph.def.DelegationException). After deleting <handler></handler> process is running correctly. Don't know if this is error in engine or in designer. Maby this kind of decision node is incorrect, and then designer should avoid this situation. My opinion is that engine should ignore empty handlers and go on without errors... -- 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

14 years

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1118) Unexpected behavier of LoggingConfigDbTest

by Jan-Philipp Bolle (JIRA)

Unexpected behavier of LoggingConfigDbTest ------------------------------------------ Key: JBPM-1118 URL: http://jira.jboss.com/jira/browse/JBPM-1118 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Jan-Philipp Bolle Assigned To: Tom Baeyens Priority: Trivial It looks like that the LoggingConfigDbTest is not working. I added in nologging.jbpm.cfg.xml the org.jbpm.logging.db.DbLoggingServiceFactory. Now I assume that the test must fail because jBPM is configured to use the loggingservice. But the test still work (is green). -- 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

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1159) Update missing suggested alternatives in deprecated JbpmSessionFactory

by Julien Kronegg (JIRA)

Update missing suggested alternatives in deprecated JbpmSessionFactory ---------------------------------------------------------------------- Key: JBPM-1159 URL: http://jira.jboss.com/jira/browse/JBPM-1159 Project: JBoss jBPM Issue Type: Bug Components: Documentation Affects Versions: jBPM jPDL 3.2.2 Environment: source code downloaded from CVS :pserver:anonymous@anoncvs.forge.jboss.com:/cvsroot/jbpm (jbpm.3) Reporter: Julien Kronegg Assigned To: Tom Baeyens Priority: Minor The class org.jbpm.db.JbpmSessionFactory is deprecated and the deprecation comment states: @deprecated use {@link org.jbpm.tc.ContextBuilder} and {@link org.jbpm.tc.db.JbpmSessionContext} instead. However, the org.jbpm.tc package is no more in the code. Thus, another suggested replacement should be provided. Contrarily of as specified in http://jira.jboss.com/jira/browse/JBPM-624 this issue is not fixed in CVS (as the code was downloaded from CVS). -- 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

14 years

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1171) make jbpm configurable to use a mail session from jndi instead of an additional config file

by Ronald van Kuijk (JIRA)

make jbpm configurable to use a mail session from jndi instead of an additional config file ------------------------------------------------------------------------------------------- Key: JBPM-1171 URL: http://jira.jboss.com/jira/browse/JBPM-1171 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Fix For: jBPM 3.3 jBPM now uses a config file for mail properties. Often (especially in JEE envs) a mail session is already configured and could be used by looking it up via jndi. jBPM should support this as well. -- 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

14 years, 1 month

4
14
0 / 0

[JBoss JIRA] Created: (JBPM-1164) Null Pointer Exception is thrown when subprocess is leave event is fired.

by Gurpreet Sahota (JIRA)

Null Pointer Exception is thrown when subprocess is leave event is fired. ------------------------------------------------------------------------- Key: JBPM-1164 URL: http://jira.jboss.com/jira/browse/JBPM-1164 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.2 Environment: Windows XP Pro, Sun JDK 1.5.0_13 Reporter: Gurpreet Sahota Assigned To: Tom Baeyens I have a process flow where process (A) calls a process state that in turn calls subprocess (B). When Subprocess "end" state is signalled then I receive a Null Pointer Exception. Following is stack trace java.lang.NullPointerException at org.jbpm.graph.node.ProcessState.leave(ProcessState.java:204) at org.jbpm.graph.exe.Token.signal(Token.java:195) at org.jbpm.graph.exe.Token.signal(Token.java:140) When debugging, it turns out that "leave" method in ProcessState tries to retrieve subProcessInstance from execution context. This is set to null causing exception. If executionContext.getToken() is used to retrieve the subProcessInstance, then it is not null. -- 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

14 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBPM-1147) iCalendar Wrapper for jBPM tasks

by Adrian Apthorp (JIRA)

iCalendar Wrapper for jBPM tasks -------------------------------- Key: JBPM-1147 URL: http://jira.jboss.com/jira/browse/JBPM-1147 Project: JBoss jBPM Issue Type: Feature Request Reporter: Adrian Apthorp Assigned To: Tom Baeyens Provide iCalendar Wrapper for jBPM tasks for HTTP and Mail channels. The following code sample is an example servlet for retrieving tasks in iCalendar format to demonstrate mapping of Taskinstance to iCalendar VTODO. [code] package org.jbpm.examples.simple.web; import java.io.IOException; import java.net.URI; import java.util.Date; import java.util.GregorianCalendar; import java.util.Iterator; import javax.servlet.ServletException; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; // Use iCal4j package import net.fortuna.ical4j.model.DateTime; import net.fortuna.ical4j.model.Property; import net.fortuna.ical4j.model.TimeZoneRegistry; import net.fortuna.ical4j.model.TimeZoneRegistryFactory; import net.fortuna.ical4j.model.component.VEvent; import net.fortuna.ical4j.model.component.VToDo; import net.fortuna.ical4j.model.component.VTimeZone; import net.fortuna.ical4j.model.property.Attach; import net.fortuna.ical4j.model.property.Attendee; import net.fortuna.ical4j.model.property.CalScale; import net.fortuna.ical4j.model.property.Comment; import net.fortuna.ical4j.model.property.Completed; import net.fortuna.ical4j.model.property.Contact; import net.fortuna.ical4j.model.property.Created; import net.fortuna.ical4j.model.property.Description; import net.fortuna.ical4j.model.property.Location; import net.fortuna.ical4j.model.property.Method; import net.fortuna.ical4j.model.property.Organizer; import net.fortuna.ical4j.model.property.Priority; import net.fortuna.ical4j.model.property.ProdId; import net.fortuna.ical4j.model.property.Version; import net.fortuna.ical4j.util.UidGenerator; import org.jbpm.JbpmConfiguration; import org.jbpm.JbpmContext; import org.jbpm.mail.AddressResolver; import org.jbpm.taskmgmt.exe.TaskInstance; import org.jbpm.context.exe.ContextInstance; import org.jbpm.graph.exe.*; import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; /** * Servlet implementation class for Servlet: ICalServlet * */ public class ICalServlet extends javax.servlet.http.HttpServlet implements javax.servlet.Servlet { static final long serialVersionUID = 1L; private static Log log = LogFactory.getLog(ICalServlet.class); private String localMachine; private String PORT = "8080"; private static final String TASK_URI = "/jbpm-console/sa/task.jsf?id="; public ICalServlet() { super(); try { localMachine = java.net.InetAddress.getLocalHost().getHostName(); log.info("Hostname of local machine: " + localMachine); } catch (java.net.UnknownHostException uhe) { log.info("Can't Retrieve Hostname"); localMachine = "localhost"; } } protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { String pathInfo = null; log.debug("Request Path:" + request.getPathInfo()); if (request.getPathInfo() != null) { pathInfo = request.getPathInfo().toLowerCase(); } boolean isTaskList = pathInfo != null && pathInfo.endsWith("tasklist.ics"); boolean isFreeBusy = pathInfo != null && pathInfo.endsWith("freebusy.ifb"); if (isTaskList) { doTaskList(request, response); } else if (isFreeBusy) { /* * doGetFreeBusy(request, response); */ } } /** * * http://localhost:8080/calendar/reply?actor=user * */ public final void doTaskList(HttpServletRequest req, HttpServletResponse resp) throws IOException { String actorName = req.getParameter("actor"); log.info("Actor:" + actorName); JbpmConfiguration jbpmConfiguration = JbpmConfiguration.getInstance(); JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); resp.setContentType("text/calendar"); try { java.util.List toDoList = jbpmContext.getTaskMgmtSession() .findTaskInstances(actorName); /* * jbpmContext.getTaskMgmtSession().findPooledTaskInstances(actorName) */ if (toDoList == null) { resp.sendError(HttpServletResponse.SC_NOT_FOUND, "No Tasks Found For User"); return; } net.fortuna.ical4j.model.Calendar calendar = new net.fortuna.ical4j.model.Calendar(); calendar.getProperties().add( new ProdId("-//aapthorp//jBPM iCal wrapper//EN")); calendar.getProperties().add(Version.VERSION_2_0); calendar.getProperties().add(CalScale.GREGORIAN); calendar.getProperties().add(Method.REQUEST); for (Iterator iter = toDoList.iterator(); iter.hasNext();) { TaskInstance task = (TaskInstance) iter.next(); ProcessInstance processInstance = task.getProcessInstance(); ContextInstance contextInstance = processInstance.getContextInstance(); TimeZoneRegistry registry = TimeZoneRegistryFactory.getInstance() .createRegistry(); String taskId = String.valueOf(task.getId()); String actorId = task.getActorId(); String taskName = task.getName(); // Due Date - This property defines the date and time that a to do is // expected to be completed. net.fortuna.ical4j.model.DateTime dueDate = new net.fortuna.ical4j.model.DateTime( task.getDueDate()); // Start Date - This property specifies when the calendar component // begins. There is no direct jBPM equivalent so we use a task variable. java.util.Calendar beginDate = new GregorianCalendar(); net.fortuna.ical4j.model.TimeZone timezone = registry .getTimeZone(beginDate.getTimeZone().getID()); net.fortuna.ical4j.model.DateTime startDate = null; if (contextInstance.hasVariable("start")) { beginDate.setTime((java.util.Date) contextInstance.getVariable( "start", task.getToken())); startDate = new net.fortuna.ical4j.model.DateTime(beginDate.getTime()); startDate.setTimeZone(timezone); } dueDate.setTimeZone(timezone); /* * Create the VTODO * * For testing purposes with user agents that can't handle VTODO's we * can creat a Vevent VEvent toDo = new VEvent(null,dueDate,taskName+" - * "+taskId); * */ log.info("Create VTODO: task - " + taskId + " start - " + startDate + " due - " + dueDate); VToDo toDo = new VToDo(startDate, dueDate, taskName + " - " + taskId); // Creation Date toDo.getProperties() .add( new Created(new net.fortuna.ical4j.model.DateTime(task .getCreate()))); // End Date a.k.a. Completed Date. This property defines the date and // time that a to-do was actually completed. if (task.getEnd() != null) { toDo.getProperties().add( new Completed( new net.fortuna.ical4j.model.DateTime(task.getEnd()))); } // Generate a UID for the toDo toDo.getProperties().add((new UidGenerator(taskId)).generateUid()); // Attach URL to Task toDo.getProperties().add( new Attach(new URI("http://" + localMachine + ":" + PORT + TASK_URI + taskId.toString()))); // Set Contact - We set a task variable for this. if (contextInstance.hasVariable("Name")) { toDo.getProperties().add( new Contact((String) contextInstance.getVariable("Name", task .getToken()))); } // Set Location - We set a task variable for this. if (contextInstance.hasVariable("Address")) { toDo.getProperties().add( new Location((String) contextInstance.getVariable("Address", task .getToken()))); } // Set Priority toDo.getProperties().add(new Priority(task.getPriority())); if (task.getDescription() != null) { toDo.getProperties().add(new Description(task.getDescription())); } java.util.List commentList = task.getComments(); if (commentList != null) { for (Iterator commentIter = commentList.iterator(); commentIter .hasNext();) { org.jbpm.graph.exe.Comment myComment = (org.jbpm.graph.exe.Comment) commentIter .next(); toDo.getProperties().add( new net.fortuna.ical4j.model.property.Comment(myComment.getId() + ":" + myComment.getTime() + ":" + myComment.getActorId() + ":" + myComment.getMessage())); } } // Set Attendee net.fortuna.ical4j.model.ParameterList attendeePL = new net.fortuna.ical4j.model.ParameterList(); attendeePL.add(new net.fortuna.ical4j.model.parameter.Cn(actorId)); attendeePL.add(new net.fortuna.ical4j.model.parameter.Role( "REQ-PARTICIPANT")); attendeePL.add(new net.fortuna.ical4j.model.parameter.PartStat( "NEEDS-ACTION")); attendeePL.add(new net.fortuna.ical4j.model.parameter.Rsvp("TRUE")); AddressResolver addressResolver = (AddressResolver) JbpmConfiguration.Configs .getObject("jbpm.mail.address.resolver"); URI attendeeURI = new URI("MAILTO", (String) addressResolver .resolveAddress(actorId), null); toDo.getProperties().add(new Attendee(attendeePL, attendeeURI)); // Set Organizer String orgAddress = getFromAddress(); if (orgAddress != null) { URI mailToURI = new URI("MAILTO", orgAddress, null); toDo.getProperties().add(new Organizer(mailToURI)); } calendar.getComponents().add(toDo); } resp.getOutputStream().write(calendar.toString().getBytes()); } catch (Exception e) { e.printStackTrace(); resp.sendError(HttpServletResponse.SC_INTERNAL_SERVER_ERROR, "Caught exception: " + e); } finally { jbpmContext.close(); } } public String getFromAddress() { if (JbpmConfiguration.Configs.hasObject("jbpm.mail.from.address")) { return JbpmConfiguration.Configs.getString("jbpm.mail.from.address"); } return "jbpm@noreply"; } } [/code] -- 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

14 years, 7 months

4
6
0 / 0

[JBoss JIRA] Created: (JBPM-1162) Problem with exception handling within the Decision nodes

by Jon Folland (JIRA)

Problem with exception handling within the Decision nodes --------------------------------------------------------- Key: JBPM-1162 URL: http://jira.jboss.com/jira/browse/JBPM-1162 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: Vaio laptop running Windows Vista, Java 1.5, JBPM 3.2.2 Reporter: Jon Folland Assigned To: Tom Baeyens I believe there may be a bug in the Decision class where exception handling is concerned which causes this failure: If the line: String transitionName = decisionHandler.decide(executionContext); ... ...in the method public void execute(ExecutionContext executionContext) throws an exception, which is caught here in the same method: raiseException(exception, executionContext); We miss the block: if (transition==null) { transition = getDefaultLeavingTransition(); log.debug("decision didn't select transition, taking default "+transition); } So when executionContext.leaveNode(transition); is called at the bottom, there wil be no transition set. I believe we need to check for a tranistion==null condition regardless of whether an excpetion has been handled. Otherwise you will never be able to handle an exception in a Decision without another unhandled exception being thrown (which kind of defeits the point :-) -- 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

14 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-1158) Missing query JobSession.findJobsWithOverdueLockTime in hibernate.queries.hbm.xml

by Julien Kronegg (JIRA)

Missing query JobSession.findJobsWithOverdueLockTime in hibernate.queries.hbm.xml --------------------------------------------------------------------------------- Key: JBPM-1158 URL: http://jira.jboss.com/jira/browse/JBPM-1158 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2.2 Environment: zip file downloaded from http://www.jboss.org/downloading/?projectId=jbossjbpm&url=http://download... Reporter: Julien Kronegg Assigned To: Tom Baeyens The org.jbpm.db.JobSession class has a findJobsWithOverdueLockTime(Date) method which use a query named "JobSession.findJobsWithOverdueLockTime". In similar methods of the same class, the queries are located in org.jbpm.db.hibernate.queries.hbm.xml, which is not the case for this query. The "JobSession.findJobsWithOverdueLockTime" string could not be found elsewhere in the project. Conclusion: the "JobSession.findJobsWithOverdueLockTime" query seems to be missing in hibernate.queries.hbm.xml (or the method should be removed from the class). -- 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

14 years, 7 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 May 2008