June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBPM-1078) Bug when designing process if node has "/" in his name

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1078?page=all ] Thomas Diesler updated JBPM-1078: --------------------------------- Assignee: (was: Tom Baeyens) > Bug when designing process if node has "/" in his name > ------------------------------------------------------ > > Key: JBPM-1078 > URL: http://jira.jboss.com/jira/browse/JBPM-1078 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM jPDL 3.2.2 > Environment: eclipse 3.3, ubuntu linux 6.10, jdk 1.5 > Reporter: Andraz Skoric > Priority: Minor > > If you have 2 nodes and the second one includes char / in his name you cannot make a transition from node 1 to node 2. Transition is pointed into upper left corner and not to node 2. If you manually code transition it looks fine, but one you restart your workspace the problem comes back. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-460) create certification questions

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-460?page=all ] Thomas Diesler updated JBPM-460: -------------------------------- Assignee: (was: Tom Baeyens) > create certification questions > ------------------------------ > > Key: JBPM-460 > URL: http://jira.jboss.com/jira/browse/JBPM-460 > Project: JBoss jBPM > Issue Type: Task > Components: Training > Reporter: Tom Baeyens > > see certification folder in my inbox -- 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

16 years, 6 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1066?page=all ] Thomas Diesler updated JBPM-1066: --------------------------------- Assignee: (was: Tom Baeyens) > equivalent of pooled-actors group functionality in mailnodes > ------------------------------------------------------------ > > Key: JBPM-1066 > URL: http://jira.jboss.com/jira/browse/JBPM-1066 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.2, jBPM jPDL 3.2.1 > 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1014) Logging in often yields an error

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1014?page=all ] Thomas Diesler updated JBPM-1014: --------------------------------- Assignee: (was: Tom Baeyens) > Logging in often yields an error > -------------------------------- > > Key: JBPM-1014 > URL: http://jira.jboss.com/jira/browse/JBPM-1014 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1 > Environment: FC6 - Sun Java 1.5.0.12 - Firefox 1.5.0.12 > Reporter: Micah Modell > > I regularly get the following error when I attempt to log in. If I go back to the console and try again from the actual page (not a reload) then it seems to remedy the problem: > 00:14:54,587 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception > javax.faces.application.ViewExpiredException: viewId:/sa/procdef.jsf - View /sa/procdef.jsf could not be restored. > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:180) > at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248) > at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) > at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:595) -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-575) delete Timer fails in Scheduler

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-575?page=all ] Thomas Diesler updated JBPM-575: -------------------------------- Assignee: (was: Tom Baeyens) > delete Timer fails in Scheduler > ------------------------------- > > Key: JBPM-575 > URL: http://jira.jboss.com/jira/browse/JBPM-575 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1 > Environment: jbpm 3.1, PostgreSQL / MS SQL Server / DB/2, jboss 4.0.4 RC1 > Reporter: maplat > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > if a timer is scheduled, which execution leeds to the process end, the timer can not be deleted, > because at the end of the process instance all timers are canceld and after this the scheduler also tries > to delete the timer > I did a change on SchedulerSession.cancelTimersForProcessInstance > (the commented code ist the original one, I also added a new named query to hibernate.queries.hbm.xml) > The change does not directly delete the timers from database, it calls the deleteTimer methode, which causes the > timers beeing deleted to be added to the deletedTimers collection. If another delete is done from the scheduler > it is ignored, because in the delete timer methode the deletedTImers collection is checked. > public void cancelTimersForProcessInstance(ProcessInstance processInstance) { > try { > /*Query query = session.getNamedQuery("SchedulerSession.deleteTimersForProcessInstance"); > query.setEntity("processInstance", processInstance); > query.executeUpdate();*/ > Query query = session.getNamedQuery("SchedulerSession.findTimersForProcessInstance"); > query.setEntity("processInstance", processInstance); > Iterator iter = query.list().iterator(); > while(iter.hasNext()) { > deleteTimer((Timer) iter.next()); > } > } catch (Exception e) { > log.error(e); > jbpmSession.handleException(); > throw new JbpmException("couldn't delete timers for process instance '"+processInstance+"'", e); > } > } > -- new named query > <query name="SchedulerSession.findTimersForProcessInstance"> > <![CDATA[ > select t from org.jbpm.scheduler.exe.Timer t > where t.processInstance = :processInstance > ]]> > </query> > I'm not sure if the deleteTimersForProcessInstance query is used somewhere else, so I left it. > If this approch is right, someone of the developers maybe can fix it in the code, I do not have access to it -- 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

16 years, 6 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1021?page=all ] Thomas Diesler updated JBPM-1021: --------------------------------- Assignee: (was: Tom Baeyens) > 3.2.1 Admin Console: Process Instance List should show duration > --------------------------------------------------------------- > > Key: JBPM-1021 > URL: http://jira.jboss.com/jira/browse/JBPM-1021 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Web Interface > Affects Versions: jBPM jPDL 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
0
0 / 0

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

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1083?page=all ] Thomas Diesler updated JBPM-1083: --------------------------------- Assignee: (was: Tom Baeyens) > Augment Assignable interface > ---------------------------- > > Key: JBPM-1083 > URL: http://jira.jboss.com/jira/browse/JBPM-1083 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-835) create strategy for dealing with example dependencies

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-835?page=all ] Thomas Diesler updated JBPM-835: -------------------------------- Assignee: (was: Tom Baeyens) > create strategy for dealing with example dependencies > ----------------------------------------------------- > > Key: JBPM-835 > URL: http://jira.jboss.com/jira/browse/JBPM-835 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > > When I created a project in Eclipse with jbpm-jpdl-3.2.Beta2 as the source there was a number of compilation issues. These I could resolve as follows: > 1) jms example - remove or comment out the offending code. This example uses APIs that do not exist in the product. > 2) org.apache.tools.ant.BuildException in src/identity/LoadIdentitiesTask required ant.jar to be added to lib > 3) my rules examples require drools-compiler-3.0.5 and drools-core-3.0.5 to be added to lib > 4) org.jbpm.jcr.jackrabbit.JackrabbitJcrServiceFactory requires jackrabbit-core-1.0.1 to be added to lib -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1076) ie. JbpmContext.getGroupTaskList(List actorIds, String taskName)

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ] Thomas Diesler updated JBPM-1076: --------------------------------- Assignee: (was: Tom Baeyens) > ie. JbpmContext.getGroupTaskList(List actorIds, String taskName) > ---------------------------------------------------------------- > > Key: JBPM-1076 > URL: http://jira.jboss.com/jira/browse/JBPM-1076 > Project: JBoss jBPM > Issue Type: Feature Request > Affects Versions: jBPM jPDL 3.2.2 > Environment: Windows XP, jBPM JDPL 3.2.2, JBoss 4.2.2, Seam 2.0.0CR3 > Reporter: Flavio Crispim > Priority: Minor > Attachments: hibernate.queries.hbm.xml.patch, JbpmContext.java.patch, TaskMgmtSession.java.patch > > > I need to use the tasks pool, but they should be a pool per task. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-479) Option to allow Tokens with activechildren not to continue transition

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-479?page=all ] Thomas Diesler updated JBPM-479: -------------------------------- Assignee: (was: Tom Baeyens) > Option to allow Tokens with activechildren not to continue transition > --------------------------------------------------------------------- > > Key: JBPM-479 > URL: http://jira.jboss.com/jira/browse/JBPM-479 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM 3.1 alpha 1 > Environment: any > Reporter: Elmo > Priority: Optional > > When a process instance (root token) is signalled in a fork, or in a subprocess, the process continues via the default leaving node. This is quite misleading. In my opinion the desired behavior would be blocking (i.e. means all child tokens must have ended) before continuing the transition. Although this can be managed through code, signalling the token (fork) by accident would give undesired results. If possible, I would like an option to stop the token from continuing if there are still active children. The code below illustrates this: > source: Token > public void signal() { > //initial checking > //proposed code: if option is used by developer, block the signal if there are active children > if( (CHECK_ACTIVECHILDREN_OPTION) && (this.hasActiveChildren()) ) > throw new IllegalStateException( "Cannot signal " + this + " if there are active children" ); > //signal routine > } > This option is false by default. I leave it to the group how they will set the option, either through the node definition (private) or to the process definition or maybe even through system properties (global). The users who will implement this must be aware of the consequences i.e. it is their responsibility to end the child tokens themselves or else it can never continue. This is only an option. I have not fully tested or did a full test case on the side effects of this, so I would appreciate if somebody could point this out because I have it implemented in my code. Thanks. > > Regards, > Elmo -- 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

16 years, 6 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 June 2008