September 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Commented: (JBPM-1448) jBPM does not initialise thread context classloader

by Bernd Ruecker (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Bernd Ruecker commented on JBPM-1448: ------------------------------------- Hi. What is the current status of this issue? I am working in the same area at the moment, so I could also have a deeper look at it, but I want to avoid duplicate work... In the current SVN HEAD I don't see any changes, so nobody started yet, right? > jBPM does not initialise thread context classloader > --------------------------------------------------- > > Key: JBPM-1448 > URL: https://jira.jboss.org/jira/browse/JBPM-1448 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Kevin Conner > Assignee: Trevor Kirby > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3 > > > jBPM does not initialise the thread context classloader when executing actions within the process. > The outcome of this decision is that code executed within the context of this action will not have access to classes/resources in the par unless the action classloader is an explicit parameter. > One example of this is the RMI marshalling layer, which has an implication on JNDI lookups. -- 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

16 years, 3 months

1
0
0 / 0

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

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-850?page=com.atlassian.jira.plugi... ] Tom Baeyens reassigned JBPM-850: -------------------------------- Assignee: Tom Baeyens > Tasks with mail notification (notify="yes") fail if the assigned actor has no e-mail address. > --------------------------------------------------------------------------------------------- > > Key: JBPM-850 > URL: https://jira.jboss.org/jira/browse/JBPM-850 > Project: JBoss jBPM > Issue Type: Patch > Affects Versions: jBPM 3.2.0 > Reporter: Bruno Dumon > Assignee: Tom Baeyens > Fix For: jBPM 3.3.0 GA > > 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1227) fix tests HibernateJobDbSessionTest and JobExecutorTimerSessionTest

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1227?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1227: --------------------------------- Fix Version/s: PVM 1.0.0 Beta2 (was: PVM 1.0.0 Beta1) Deferred to Beta2 > fix tests HibernateJobDbSessionTest and JobExecutorTimerSessionTest > ------------------------------------------------------------------- > > Key: JBPM-1227 > URL: https://jira.jboss.org/jira/browse/JBPM-1227 > Project: JBoss jBPM > Issue Type: Task > Components: PVM > Reporter: Tom Baeyens > Fix For: PVM 1.0.0 Beta2 > > > I've added some comments as TODO's in the code. The complete code is commented. > First fix test HibernateJobDbSessionTest and then and JobExecutorTimerSessionTest and the former contains more instructions/comments. -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-1223) Add "and" to duration language in timers

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1223?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1223: --------------------------------- Fix Version/s: PVM 1.0.0 Beta2 (was: PVM 1.0.0 Beta1) Deferred to Beta2 > Add "and" to duration language in timers > ---------------------------------------- > > Key: JBPM-1223 > URL: https://jira.jboss.org/jira/browse/JBPM-1223 > Project: JBoss jBPM > Issue Type: Task > Components: PVM > Environment: All > Reporter: Jim Rigsbee > Priority: Minor > Fix For: PVM 1.0.0 Beta2 > > > Currently the PDL allows for duration expressions of the type <quantity> {business} <unit>, e.g. 5 business hours or 5 days. Please expand this to allow the word "and" between multiple nodes. The time should be aggregated as milliseconds. Some examples, > 5 business days and 2 hours, > 1 month and 25 days and 2 minutes > Tom's suggestion is that if business appears anywhere in the string that the entire duration is considered to be in "business time". -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1420) jBPM eclipse tools setup broken

by Heiko Braun (JIRA)

jBPM eclipse tools setup broken ------------------------------- Key: JBPM-1420 URL: https://jira.jboss.org/jira/browse/JBPM-1420 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: Productization Reporter: Heiko Braun Assignee: Koen Aers Priority: Critical Fix For: JBossBPM-3.3.0 The eclipse tools require a jBPM installation (Preferences>jBPM>Runtime Locations). This doesn't work with the new maven layout anymore. -- 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

16 years, 4 months

3
14
0 / 0

[JBoss JIRA] Created: (JBPM-1408) Consolidate hudson QA for JBossBPM

by Heiko Braun (JIRA)

Consolidate hudson QA for JBossBPM ---------------------------------- Key: JBPM-1408 URL: https://jira.jboss.org/jira/browse/JBPM-1408 Project: JBoss jBPM Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Productization Affects Versions: JBossBPM-3.3.0 Reporter: Heiko Braun Assignee: Heiko Braun Currently I see many different QA runs: - http://hudson.jboss.org/hudson/view/SOA/ - http://hudson.qa.jboss.com/hudson/view/jbpm/ -- 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

16 years, 4 months

3
20
0 / 0

[JBoss JIRA] Created: (JBPM-1313) Migrate build to maven

by Heiko Braun (JIRA)

Migrate build to maven ---------------------- Key: JBPM-1313 URL: http://jira.jboss.com/jira/browse/JBPM-1313 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Heiko Braun -- 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, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-1197) Switch jBPM source repository to SVN

by Thomas Diesler (JIRA)

Switch jBPM source repository to SVN ------------------------------------ Key: JBPM-1197 URL: http://jira.jboss.com/jira/browse/JBPM-1197 Project: JBoss jBPM Issue Type: Task Reporter: Thomas Diesler Assigned To: Koen Aers Fix For: jBPM jPDL 3.2.4 Please assign back to be when 3.2.3 is tagged -- 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, 4 months

4
12
0 / 0

[JBoss JIRA] Created: (JBPM-1733) createSchema is called for every DB test

by Thomas Diesler (JIRA)

createSchema is called for every DB test ---------------------------------------- Key: JBPM-1733 URL: https://jira.jboss.org/jira/browse/JBPM-1733 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Components: jPDL 3 Reporter: Thomas Diesler Priority: Blocker Fix For: jBPM 3.3.0 This issue prevents meaningful test runs on postgresql hsqldb: 1.5 min mysql: 25min postgre: 5h public void setUp() throws Exception { log.debug("### starting " + getLongName() + " ####################################################"); super.setUp(); try { // TODO: This creates the schema on EVERY test createSchema(); // If a clean DB is realy needed this should perhaps be done //cleanSchema(); createJbpmContext(); initializeMembers(); } catch (Exception ex) { // Note, that if setUp fails a call to tearDown will not happen. log.error("Exception is setUp, tearDown will not get called", ex); throw ex; } } -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBPM-1452) JbpmConfiguration assumes the object factory has a jbpm.job.executor entry

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1452?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1452: --------------------------------- Comment: was deleted > JbpmConfiguration assumes the object factory has a jbpm.job.executor entry > -------------------------------------------------------------------------- > > Key: JBPM-1452 > URL: https://jira.jboss.org/jira/browse/JBPM-1452 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: jBPM 3.3.0 CR1 > Environment: 3.3 snapshot > Spring > Reporter: Alejandro Guizar > Assignee: Alejandro Guizar > Fix For: jBPM 3.3.0 CR1 > > > The following exception is thrown while completing a task that ends a process. The application runs with the 3.3 snapshot JAR. > org.jbpm.configuration.ConfigurationException: name 'jbpm.job.executor' is not defined in the configuration. configured names: [resource.hibernate.queries.hbm.xml, jbpm.msg.wait.timout, jbpm.task.instance.factory, resource.default.modules, resource.varmapping, resource.business.calendar, resource.action.types, resource.parsers, default.jbpm.context, resource.node.types, resource.converter, jbpm.variable.resolver, jbpm.byte.block.size] > at org.jbpm.configuration.ObjectFactoryImpl.createObject(ObjectFactoryImpl.java:76) > at org.jbpm.JbpmConfiguration.getJobExecutor(JbpmConfiguration.java:603) > at org.jbpm.scheduler.db.DbSchedulerService.<init>(DbSchedulerService.java:51) > at org.jbpm.scheduler.db.DbSchedulerServiceFactory.openService(DbSchedulerServiceFactory.java:32) > at org.jbpm.svc.Services.getService(Services.java:156) > at org.jbpm.svc.Services.getCurrentService(Services.java:94) > at org.jbpm.graph.exe.ProcessInstance.end(ProcessInstance.java:328) > at org.jbpm.graph.exe.Token.notifyParentOfTokenEnd(Token.java:329) > at org.jbpm.graph.exe.Token.end(Token.java:301) > at org.jbpm.graph.exe.Token.end(Token.java:251) > at org.jbpm.graph.node.EndState.execute(EndState.java:59) > The 3.3 snapshot is looking for 'jbpm.job.executor' which is defined in the default.jbpm.cfg.xml, but which the application does not have in its jbpm.cfg.xml. It works with 3.2.2. The JobExecutor is set up manually in a Spring configuration. -- 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

16 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues September 2008