January 2009 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-1080) Limit BAM Query to input data for simulation to time range doesn't work

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1080?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1080. ---------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > Limit BAM Query to input data for simulation to time range doesn't work > ----------------------------------------------------------------------- > > Key: JBPM-1080 > URL: https://jira.jboss.org/jira/browse/JBPM-1080 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Simulation > Affects Versions: jBPM 3.2.2 > Reporter: Bernd Ruecker > Priority: Minor > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The GetSimulationInputCommand has a parameter "fromTimeOfDay" and "tillTimeOfDay". This should be included in the hibernate quries to supprto to query statistical data only for special times (for example shifts). > Unfortunately, comparing the time is not really easy with supporting different databases. In MySQL, there is a TIME(xxx) function, HSQL only supports HOUR(xxx) and MINUTE(xxx). > Si I skipped it for the moment. The mySQL ready statements are commented out in the queries file. > Co currently, ALL statistics from all 24 hours are returned. -- 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

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1083) Augment Assignable interface

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1083?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1083. ---------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > Augment Assignable interface > ---------------------------- > > Key: JBPM-1083 > URL: https://jira.jboss.org/jira/browse/JBPM-1083 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.2.2 > Environment: All > Reporter: s b > > The Assignable interface needs additional methods defined for efficient code development: > getName() > getId() > getActorId() > getPooledActors() > Without these methods, casting and "instanceof" cases are required and much duplicate code for processing of assignments to both SwimlaneInstance and TaskInstance. -- 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

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1103) Make repeat accept EL in addition to the already existing businesscalendar

by Ronald van Kuijk (JIRA)

Make repeat accept EL in addition to the already existing businesscalendar -------------------------------------------------------------------------- Key: JBPM-1103 URL: http://jira.jboss.com/jira/browse/JBPM-1103 Project: JBoss jBPM Issue Type: Feature Request Affects Versions: jBPM jPDL 3.2.2 Reporter: Ronald van Kuijk Assigned To: Ronald van Kuijk Priority: Optional Fix For: jBPM 3.3 Just like with the dueate itself.... Note: make sure to refacor this code into a new class in the calendar package -- 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

15 years, 4 months

2
2
0 / 0

[JBoss JIRA] Resolved: (JBPM-1021) 3.2.1 Admin Console: Process Instance List should show duration

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1021?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1021. ---------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > 3.2.1 Admin Console: Process Instance List should show duration > --------------------------------------------------------------- > > Key: JBPM-1021 > URL: https://jira.jboss.org/jira/browse/JBPM-1021 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Console > Affects Versions: jBPM 3.2.1 > Reporter: Burr Sutter > > Currently the begin & end times are shown, a common request from users is to know how long it takes complete a particular process instance. -- 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

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1074) Allow simple configuration of jbpm-mail.war.

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1074?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1074. ---------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > Allow simple configuration of jbpm-mail.war. > -------------------------------------------- > > Key: JBPM-1074 > URL: https://jira.jboss.org/jira/browse/JBPM-1074 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Console > Affects Versions: jBPM 3.2.2 > Environment: Jboss AS > Reporter: Chris Sweeney > Attachments: InboxServlet.java, jbpm-mail.war, web.xml > > > Allow the port and page refresh to be configured using "standard" web.xml servlet init parameters. -- 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

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1067) token.getAvailableTransitions() -- need equivalent that returns ordered list.

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1067?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1067. ---------------------------------- Fix Version/s: (was: jBPM 3.3.2 GA ) Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > token.getAvailableTransitions() -- need equivalent that returns ordered list. > ----------------------------------------------------------------------------- > > Key: JBPM-1067 > URL: https://jira.jboss.org/jira/browse/JBPM-1067 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.2.2 > Environment: All OS > Reporter: s b > > This feature request is requesting: > 1) API which adds a version of token.getAvailableTransitions() which returns an ordered List that preserves the order of the transitions as defined in the processdefinition.xml file for the node, rather than returning an unordered Set object. > 2) Also request that TaskInstance.getAvailableTransitions() be modified to return an ordered list rather than a randomly ordered list by calling the new method. > For example: > ------------------------ > public class TaskInstance extends VariableContainer implements Assignable { > ... > public List getAvailableTransitions() { > List transitions = null; > if ( (! isLast()) > && (token!=null) > ) { > transitions = token.getAvailableTransitionsList(); // using new method > } > return transitions; > } > ... > ---------------------------------------- > Problem: > node.getLeavingTransitions() appears to preserve the order, but the order is apparently lost when the transistions are added to the Set which is returned by token.getAvailableTransitions(). > Preserving the ordering is highly useful when implementing a minimal data-driven interface which presents the user with the transitions to choose from. The designer could exercise some control over the presentation of the choices if only the order were preserved as defined in the processdefinition.xml file. > Solution: > Make a clone of "token.getAvailableTransitions()", name it "token.getAvailableTransitionsList()", and add the filtered transitions to a List instead of to a Collection, and return the list. Make sure the order is preserved the same as the transitions were defined in the "processdefinition.xml" file. > Modify "TaskInstance.getAvailableTransitions()" to call token.getAvailableTransitionsList(). > Summary: > Although workarounds exist with existing code, it would be very helpful (and consistent I think) to provide an API that retrieves a list of the "available transitions" that is ordered as defined in the processdefinition.xml file instead of an unordered Set or List as is currently available. -- 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

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1068) Possibility of UITaskFormButtonBase to use child action tags such as it done with h:commandButton

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1068?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1068. ---------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > Possibility of UITaskFormButtonBase to use child action tags such as it done with h:commandButton > ------------------------------------------------------------------------------------------------- > > Key: JBPM-1068 > URL: https://jira.jboss.org/jira/browse/JBPM-1068 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Console > Affects Versions: jBPM 3.2.1 > Reporter: Vt Ysh > Priority: Optional > > If i am trying to put custom action tags between for example <tf:saveButton value="Save"></tf:saveButton > such as it can be done with h:commandButton i am getting NullPointer exception with the next stack trace: > java.lang.NullPointerException > at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.getEnclosingForm(UITask > FormButtonBase.java:30) > at org.jbpm.jsf.taskform.ui.UITaskFormButtonBase.addActionListener(UITas > kFormButtonBase.java:44) > at org.jbpm.jsf.core.handler.AbstractHandler.apply(AbstractHandler.java: > 64) > at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH > andler.java:314) > at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java > :169) > at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa > ndler.java:47) > at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH > andler.java:314) > at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java > :169) > at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa > ndler.java:47) > at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH > andler.java:314) > at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java > :169) > at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa > ndler.java:47) > at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH > andler.java:314) > at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java > :169) > at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH > andler.java:314) > at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java > :169) > at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa > ndler.java:47) > at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentH > andler.java:314) > at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java > :169) > at com.sun.facelets.tag.ui.DefineHandler.apply(DefineHandler.java:58) > at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.j > ava:128) > at com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(Def > aultFaceletContext.java:306) > at com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(Default > FaceletContext.java:279) > at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68) > at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa > ndler.java:47) > at test.facelets.IfHandler.apply(IfHandler.java:33) > at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa > ndler.java:47) > at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.jav > a:49) > at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHa > ndler.java:47) > at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java: > 25) > at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248) > at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294) > at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273) > at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFac > eletContext.java:143) > at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.j > ava:113) > at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.jav > a:49) > at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java: > 25) > at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95) > at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java > :503) > at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.jav > a:546) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrap > per.java:178) > at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePha > se.java:106) > at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl > icationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF > ilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi > lter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl > icationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF > ilterChain.java:173) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV > alve.java:213) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV > alve.java:178) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit > yAssociationValve.java:175) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv > e.java:74) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j > ava:126) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j > ava:105) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal > ve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav > a:148) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java > :869) > at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p > rocessConnection(Http11BaseProtocol.java:664) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo > int.java:527) > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor > kerThread.java:112) > at java.lang.Thread.run(Thread.java:595) > Seems that problem can be in HtmlCommandButton.getParent() method. Is there any suggestions how to fix this issue? -- 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

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1066) equivalent of pooled-actors group functionality in mailnodes

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1066?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1066. ---------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > equivalent of pooled-actors group functionality in mailnodes > ------------------------------------------------------------ > > Key: JBPM-1066 > URL: https://jira.jboss.org/jira/browse/JBPM-1066 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.2.1, jBPM 3.2.2 > Environment: any > Reporter: Ross McDonald > Priority: Minor > > It would be nice to be able to specify a group to mail to within mail nodes, to save having to put semicolon separated actors in. This would enable the database to control who is going to be emailed, and avoid the need to keep updating processes etc -- 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

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1054) deprecate expression on action in favour of execute

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1054?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1054. ---------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > deprecate expression on action in favour of execute > --------------------------------------------------- > > Key: JBPM-1054 > URL: https://jira.jboss.org/jira/browse/JBPM-1054 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Affects Versions: jBPM 3.2.1 > Reporter: Pete Muir > Priority: Critical > > As discussed on the forum, add an execute attribute (as an alias to expression) to the action element, and (TBD) deprecate the expression. -- 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

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1052) getAllTaskInstances(), getAllProcessInstances()

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1052?page=com.atlassian.jira.plug... ] Thomas Diesler resolved JBPM-1052. ---------------------------------- Resolution: Out of Date Out of date for all Tasks and Feature Requests created before 1-Jan-2008 > getAllTaskInstances(), getAllProcessInstances() > ----------------------------------------------- > > Key: JBPM-1052 > URL: https://jira.jboss.org/jira/browse/JBPM-1052 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.2.0, jBPM 3.2.1 > Reporter: s b > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > Businesses often want a "super manager" to have the ability to see and work on the tasks of all users. With the current jBPM, it is very difficult to generate a list of all TaskInstances. > The feature requested is a method for listing all TaskInstances regardless of user. It appears to be a simple variation on the current methods which request TaskInstances by ActorId or an array of ActorIds. > One possibility might be to modify the query used by TaskManagementSession.findTaskInstances(String actorId) to use the SQL "LIKE" operator instead of "=" so that the % wildcard could be used to retrieve all TaskInstances. I don't know if that is portable to all databases; it works well for Oracle. > It has been suggested that this feature can be created as custom code, but custom code becomes very expensive to maintain and integrate with new releases of jBPM for small development companies like ours. > A similar feature to retrieve all ProcessInstances regardless of ProcessDefinition would also be highly useful for similar reasons. > A criticism is that the method would introduce scalability / performance problems. That is always an issue that is difficult to avoid completely depending on the application. For example, a business that has thousands of workers all performing the same workflow could generate a very large list using "GraphSession.findProcessInstances(long processDefinitionId)" which would be on the same order as a hypothetical "TaskManagementSession.getAllTaskInstances()" for that particular application. -- 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

15 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues January 2009