October 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBPM-2) Initial Business Intelligence (BI) capabilities

by Heiko Braun (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2?page=com.atlassian.jira.plugin.... ] Heiko Braun updated JBPM-2: --------------------------- JBoss Forum Reference: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183956 > Initial Business Intelligence (BI) capabilities > ----------------------------------------------- > > Key: JBPM-2 > URL: https://jira.jboss.org/jira/browse/JBPM-2 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Environment: N/A > Reporter: Ronald van Kuijk > Assignee: Heiko Braun > Fix For: jBPM 3.3.0 GA > > > JBoss jBPM should provide information on how processes are or have been running. Some people would call this BAM (Business Activity Monitoring), some call it BI (Business Intelligence) Some info can be found on http://www.javareport.com/article.asp?id=9238 and http://bizintelligencepipeline.com/howto/showArticle.jhtml?articleId=4990... > 1. jBPM should store the duration and start date of a state/process in the logs > 2. Write some detailed info on wiki > 3. Show processinstance and data > 4. day/week/month overviews > 5. near realtime data per process > 6. produce graphs of day/week/month overviews > Some more ideas i got from a requirements document... > - Number of cases processed in through a particular process definition > - Number of cases flowing through a particular activity > - Longest work item delay by activity > - Workitems awaiting a particular task > - Workitems in a specific worklist claimed and/or completed by a particular user > - Longest end-to-end delay > - Mean time to approve by activity by participant > - Mean end-to-end completion time. > as background info, here's what the competition says about BAM: > http://appian.com/AppianEnt/Analytics/analytics.html > http://www.webmethods.com/meta/default/folder/0000005936 > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/introduc... > http://www.tibco.com/software/business_optimization/activity_monitoring.j... > http://www.vitria.com/products/platform/bam.html > http://looselycoupled.com/glossary/BAM -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1779) Resolve dependency on gwt-console for enterprise

by Thomas Diesler (JIRA)

Resolve dependency on gwt-console for enterprise ------------------------------------------------- Key: JBPM-1779 URL: https://jira.jboss.org/jira/browse/JBPM-1779 Project: JBoss jBPM Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Priority: Critical Fix For: jBPM 3.3.0 GA The reactor build order does not include the gwt console [INFO] Reactor build order: [INFO] JBoss jBPM3 [INFO] JBoss jBPM3 - Core [INFO] JBoss jBPM3 - Identity [INFO] JBoss jBPM3 - 4JSF [INFO] JBoss jBPM3 - Console [INFO] JBoss jBPM3 - Enterprise [INFO] JBoss jBPM3 - Enterprise (JAR) [INFO] JBoss jBPM3 - Enterprise (EAR) [INFO] JBoss jBPM3 - Examples [INFO] JBoss jBPM3 - Simulation which leads to [INFO] ------------------------------------------------------------------------ [INFO] Building JBoss jBPM3 - Enterprise (EAR) [INFO] task-segment: [install] [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. Missing: ---------- 1) org.jbpm.jbpm3:gwt-console-server-war:war:3.3.0-SNAPSHOT This issue will hit everybody wanting to start with jbpm. The build build should not rely on the artefact being installed previously manually. Why is it necessary for enterprise ear to have a dependency on the gwt console? -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBPM-1449) [WoD] TagLibraryConfig loadImplicit errors

by Thomas Diesler (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1449?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1449: --------------------------------- Summary: [WoD] TagLibraryConfig loadImplicit errors (was: com.sun.facelets.compiler.TagLibraryConfig loadImplicit errors) > [WoD] TagLibraryConfig loadImplicit errors > ------------------------------------------ > > Key: JBPM-1449 > URL: https://jira.jboss.org/jira/browse/JBPM-1449 > Project: JBoss jBPM > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Engine > Reporter: Len DiMaggio > Assignee: Thomas Diesler > Priority: Minor > Fix For: SOA 4.3, jBPM 3.3.0 GA > > > Platform JIRA for project JIRA: JBPM-1065 -- 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, 2 months

1
0
0 / 0

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

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Tom Baeyens reassigned JBPM-1448: --------------------------------- Assignee: Bernd Ruecker (was: Tom Baeyens) > 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: Bernd Ruecker > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > 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, 2 months

1
0
0 / 0

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

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1448: ----------------------------------- added a test and a small fix: Replaced line 136 in class Delegation : ClassLoader classLoader = JbpmConfiguration.getProcessClassLoader(processDefinition); with ClassLoader classLoader = Thread.currentThread().getContextClassLoader(); Bernd, can you verify if this update makes sense in your overall ideas for these classloader updates ? I also added test org.jbpm.jpdl.par.ProcessClassLoaderTest. There are 2 TODO's in there. Bernd, could you look at those 2 extra tests that should be created. Give me an update thursday evening. I can take over if you don't have the time. > 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: Tom Baeyens > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPM-756) log.debug calls are unprotected

by Ronald van Kuijk (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-756?page=com.atlassian.jira.plugi... ] Ronald van Kuijk reassigned JBPM-756: ------------------------------------- Assignee: (was: Ronald van Kuijk) > log.debug calls are unprotected > ------------------------------- > > Key: JBPM-756 > URL: https://jira.jboss.org/jira/browse/JBPM-756 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.2 > Environment: Window XP, Java 5 > Reporter: Dave Caruana > > Within org.jbpm.context.exe.VariableContainer there are calls to log.debug. In particular: > line 156: log.debug("create variable '"+name+"' in '"+this+"' with value '"+value+"'"); > line 160: log.debug("update variable '"+name+"' in '"+this+"' to value '"+value+"'"); > However, they are unprotected i.e. the method is called even if debug logging is not switched on. This is not too much of a problem if the variable value is of a primitive type, but sometimes, values can be complex (including their toString()). > "if (log.isDebugEnabled())" statements are missing. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPM-756) log.debug calls are unprotected

by Ronald van Kuijk (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-756?page=com.atlassian.jira.plugi... ] Ronald van Kuijk reassigned JBPM-756: ------------------------------------- Assignee: Ronald van Kuijk > log.debug calls are unprotected > ------------------------------- > > Key: JBPM-756 > URL: https://jira.jboss.org/jira/browse/JBPM-756 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.1.2 > Environment: Window XP, Java 5 > Reporter: Dave Caruana > Assignee: Ronald van Kuijk > > Within org.jbpm.context.exe.VariableContainer there are calls to log.debug. In particular: > line 156: log.debug("create variable '"+name+"' in '"+this+"' with value '"+value+"'"); > line 160: log.debug("update variable '"+name+"' in '"+this+"' to value '"+value+"'"); > However, they are unprotected i.e. the method is called even if debug logging is not switched on. This is not too much of a problem if the variable value is of a primitive type, but sometimes, values can be complex (including their toString()). > "if (log.isDebugEnabled())" statements are missing. -- 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, 2 months

1
0
0 / 0

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

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Work on JBPM-1448 started by Tom Baeyens. > 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: Tom Baeyens > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > 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, 2 months

1
0
0 / 0

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

by Tom Baeyens (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-1448?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1448: ----------------------------------- i'm writing an extra test to see if the context classloader is properly set and restored around execution of an action. > 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: Tom Baeyens > Priority: Critical > Fix For: SOA 4.2 CP03, SOA 4.3, jBPM 3.3.0 GA > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-1722) Fix or Remove MailTest

by Thomas Diesler (JIRA)

Fix or Remove MailTest ---------------------- Key: JBPM-1722 URL: https://jira.jboss.org/jira/browse/JBPM-1722 Project: JBoss jBPM Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: jBPM 3.3.0 Caused by: org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.jbpm.graph.exe.Token#21] at org.hibernate.persister.entity.AbstractEntityPersister.check(AbstractEntityPersister.java:1769) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2412) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2312) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2612) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:96) -- 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, 2 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2008