May 2008 - jbpm-issues - Jboss List Archives

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

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1076?page=all ] Ronald van Kuijk updated JBPM-1076: ----------------------------------- Fix Version/s: jBPM 3.3 Priority: Minor (was: Major) or so much sooner as possible > 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 > Assigned To: Tom Baeyens > Priority: Minor > Fix For: jBPM 3.3 > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-850) Tasks with mail notification (notify="yes") fail if the assigned actor has no e-mail address.

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-850?page=all ] Ronald van Kuijk updated JBPM-850: ---------------------------------- Fix Version/s: jBPM jPDL 3.2.4 > Tasks with mail notification (notify="yes") fail if the assigned actor has no e-mail address. > --------------------------------------------------------------------------------------------- > > Key: JBPM-850 > URL: http://jira.jboss.com/jira/browse/JBPM-850 > Project: JBoss jBPM > Issue Type: Patch > Affects Versions: jBPM jPDL 3.2 beta 2 > Reporter: Bruno Dumon > Assigned To: Tom Baeyens > Fix For: jBPM jPDL 3.2.4 > > Attachments: noaddress_mail_patch.txt > > > In our system, it can occur users have not configured an email address, in which case they should not (and cannot) receive email notifications. So our AddressResolver implementation returns a null email address in that case. > Currently this will make jBPM try to send a mail with no recipients, causing JavaMail to raise an exception. > The attached patch (against current CVS) changes things such that a mail is not send when there are no recipients. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1060) Add EL support for Timer properties

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1060?page=comments#action_12412828 ] Ronald van Kuijk commented on JBPM-1060: ---------------------------------------- again, can someone verify? I'm triaging issues and want to close a many as possible. > Add EL support for Timer properties > ----------------------------------- > > Key: JBPM-1060 > URL: http://jira.jboss.com/jira/browse/JBPM-1060 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Affects Versions: jBPM jPDL 3.2.2 > Reporter: Fabien Coppens > Assigned To: Tom Baeyens > > It would be very useful to be able to obtain Timer properties (such as duedate) from implicit variables such as ContextInstance. -- 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, 7 months

1
0
0 / 0

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

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-479?page=all ] Ronald van Kuijk updated JBPM-479: ---------------------------------- Fix Version/s: jBPM 4.0 activityinstances in pvm will already have this. > 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 > Assigned To: Tom Baeyens > Priority: Optional > Fix For: jBPM 4.0 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-1061) jBPM creates second Hibernate Session Factory when used with CMT

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1061?page=comments#action_12412821 ] Ronald van Kuijk commented on JBPM-1061: ---------------------------------------- could this be the cause of the problems that arise when ending a process and jbpm is not the one managing the transactions? > jBPM creates second Hibernate Session Factory when used with CMT > ---------------------------------------------------------------- > > Key: JBPM-1061 > URL: http://jira.jboss.com/jira/browse/JBPM-1061 > Project: JBoss jBPM > Issue Type: Bug > Affects Versions: jBPM jPDL 3.2.2 > Environment: jBOSS AS 4.2 > jBOSS SEAM 2.0.0 > Reporter: Marcus Schmidke > Assigned To: Tom Baeyens > > When trying to use CMT for jBPM and injecting JBoss' Hibernate Session into jbpmContext, jBPM will earlier or later create a second (incomplete) Hibernate Session Factory, for example when HibernateLongIdMatcher.matches() method calls jbpmContext.getSessionFactory(). -- 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, 7 months

1
0
0 / 0

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

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1021?page=all ] Ronald van Kuijk updated JBPM-1021: ----------------------------------- Fix Version/s: jBPM 3.3 > 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 > Assigned To: Tom Baeyens > Fix For: jBPM 3.3 > > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1019) 3.2.1 Admin Console: You can signal "ended" tokens/instances, causes an exception

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1019?page=all ] Ronald van Kuijk resolved JBPM-1019. ------------------------------------ Resolution: Won't Fix a new, seam based console is under development... so won't fix.... > 3.2.1 Admin Console: You can signal "ended" tokens/instances, causes an exception > --------------------------------------------------------------------------------- > > Key: JBPM-1019 > URL: http://jira.jboss.com/jira/browse/JBPM-1019 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1 > Reporter: Burr Sutter > Assigned To: Tom Baeyens > > Signal shouldn't be an option for a token/process instance which has ended, right? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPM-1011) 3.2.1 Admin Console: Logout after a timeout

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-1011?page=all ] Ronald van Kuijk resolved JBPM-1011. ------------------------------------ Resolution: Won't Fix a new console is 'under development' and will be seam based, no gravel anymore, so won't fix > 3.2.1 Admin Console: Logout after a timeout > ------------------------------------------- > > Key: JBPM-1011 > URL: http://jira.jboss.com/jira/browse/JBPM-1011 > Project: JBoss jBPM > Issue Type: Bug > Components: Web Interface > Affects Versions: jBPM jPDL 3.2.1 > Reporter: Burr Sutter > Assigned To: Tom Baeyens > Priority: Minor > > Follow these steps using the 3.2.1 jPDL Suite > - Bring up the jBPM Admin Console: http://localhost:8080/jbpm-console in a browser > - Login: admin, admin > - Wait N Minutes for web session to timeout (I didn't look to see what the default was) > - Select "Log Out" from the top right-hand corner of the Admin Console > - Login: admin, admin > The following exception shows up. > 15:17:05,421 WARN [lifecycle] phase(RESTORE_VIEW 1,com.sun.faces.context.FacesC > ontextImpl@1bc5ebf) threw exception: java.lang.NullPointerException null > org.jboss.gravel.common.phase.GravelPhaseListener.afterPhase(GravelPhaseListener > .java:112) > com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) > com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) > javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt > erChain.java:290) > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain. > java:206) > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:9 > 6) > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt > erChain.java:235) > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain. > java:206) > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2 > 30) > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1 > 75) > And some more info: > 15:17:05,421 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet > threw exception > javax.faces.application.ViewExpiredException: viewId:/sa/token.jsf - View /sa/to > ken.jsf could not be restored. > at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.jav > a:187) > at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) > 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(Appl -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-397) Impossible to access to the process files on the filesystem (files-{i})

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-397?page=all ] Ronald van Kuijk closed JBPM-397. --------------------------------- Resolution: Out of Date > Impossible to access to the process files on the filesystem (files-{i}) > ----------------------------------------------------------------------- > > Key: JBPM-397 > URL: http://jira.jboss.com/jira/browse/JBPM-397 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 > Reporter: Carine Courbis > Assigned To: Tom Baeyens > > Problem when the process files are stored on the filesystem. > Each time a file is needed at instance execution, the system creates > a new directory files-{i} in ${jbpm.files.dir} directory and thus fails > to find the file. > The probleme seems located in the class FileDefinition line 193 as the > variable dir is always null. > Carine -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPM-697) The "business days" value for "due date" attribute of "task" node does not work properly.

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-697?page=all ] Ronald van Kuijk closed JBPM-697. --------------------------------- Resolution: Out of Date is still an issue, please reopen > The "business days" value for "due date" attribute of "task" node does not work properly. > ----------------------------------------------------------------------------------------- > > Key: JBPM-697 > URL: http://jira.jboss.com/jira/browse/JBPM-697 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Environment: Windows XP > Reporter: Amit Verma > Assigned To: Tom Baeyens > Priority: Minor > Attachments: BusinessCalendarTest.java, DayPart.java > > > The "business days" value for "due date" attribute of "task" node does not work properly. Hence the due date field of task instance does not show the correct value > The problem is with add method of DayPart class. > When we change the way dayPartEndDate object is being created FROM > Date dayPartEndDate = new Date(date.getTime() + duration.milliseconds) ; > TO > Date dayPartEndDate = new Date(date.getTime() + millisecondsInThisDayPart ); > the add method works properly > The variable "millisecondsInThisDayPart" represents the duration of dayPart not duration.milliseconds, which represent the entire duration scheduled for the 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, 7 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 May 2008