October 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Created: (JBPM-1790) Process deployment

by Heiko Braun (JIRA)

Process deployment ------------------ Key: JBPM-1790 URL: https://jira.jboss.org/jira/browse/JBPM-1790 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun -- 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
2
0 / 0

[JBoss JIRA] Created: (JBPM-1789) Process instance management

by Heiko Braun (JIRA)

Process instance management --------------------------- Key: JBPM-1789 URL: https://jira.jboss.org/jira/browse/JBPM-1789 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 Beta1 -- 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
1
0 / 0

[JBoss JIRA] Created: (JBPM-1788) Process definition management

by Heiko Braun (JIRA)

Process definition management ----------------------------- Key: JBPM-1788 URL: https://jira.jboss.org/jira/browse/JBPM-1788 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: GWT Console 1.0.0 Beta1 -- 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
1
0 / 0

[JBoss JIRA] Created: (JBPM-1721) Fix or Remove JobLoadJoinTest

by Thomas Diesler (JIRA)

Fix or Remove JobLoadJoinTest ----------------------------- Key: JBPM-1721 URL: https://jira.jboss.org/jira/browse/JBPM-1721 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.HibernateException: instance not of expected entity type: org.jbpm.context.exe.variableinstance.JcrNodeInstance is not a: org.jbpm.context.exe.VariableInstance at org.hibernate.persister.entity.AbstractEntityPersister.getSubclassEntityPersister(AbstractEntityPersister.java:3640) at org.hibernate.impl.SessionImpl.getEntityPersister(SessionImpl.java:1347) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:180) -- 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
5
0 / 0

[JBoss JIRA] Created: (JBPM-1728) Cleanup jboss.org Wiki

by Thomas Diesler (JIRA)

Cleanup jboss.org Wiki ---------------------- Key: JBPM-1728 URL: https://jira.jboss.org/jira/browse/JBPM-1728 Project: JBoss jBPM Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler There seems to be a lot of stale content on http://wiki.jboss.org/auth/wiki/JbpmWiki Please cleanup the wiki and possibly migrate the content to http://jbpm.dyndns.org/jbpmwiki/index.php?title=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, 2 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBPM-2) Add an analytical dashboard to the console

by Heiko Braun (JIRA)

[ https://jira.jboss.org/jira/browse/JBPM-2?page=com.atlassian.jira.plugin.... ] Heiko Braun updated JBPM-2: --------------------------- Fix Version/s: GWT Console 1.0.0 CR1 (was: GWT Console 1.0.0 GA) > Add an analytical dashboard to the console > ------------------------------------------ > > Key: JBPM-2 > URL: https://jira.jboss.org/jira/browse/JBPM-2 > Project: JBoss jBPM > Issue Type: Feature Request > Components: BI and BAM > Environment: N/A > Reporter: Ronald van Kuijk > Assignee: Heiko Braun > Fix For: GWT Console 1.0.0 CR1 > > > 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] Resolved: (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 resolved JBPM-1448. ------------------------------- Resolution: Done hopefully it stays resolved this 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: 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: ----------------------------------- i got it fixed locally. after being able to reproduce it locally. will try on hudson now. > 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: ----------------------------------- i can reproduce locally, but not yet in my eclipse IDE. i have added some debugging that logs the class loaders. log.info("context classloader: "+Thread.currentThread().getContextClassLoader()); log.info("parent of context classloader: "+Thread.currentThread().getContextClassLoader().getParent()); log.info("class classloader: "+getClass().getClassLoader()); log.info("parent of class classloader: "+getClass().getClassLoader().getParent()); when it succeeds, this is the logging 18:17:37,031 INFO [ResourceAction] context classloader: org.jbpm.instantiation.ProcessClassLoader@1015a9e 18:17:37,031 INFO [ResourceAction] parent of context classloader: sun.misc.Launcher$AppClassLoader@11b86e7 18:17:37,031 INFO [ResourceAction] class classloader: org.jbpm.instantiation.ProcessClassLoader@1015a9e 18:17:37,031 INFO [ResourceAction] parent of class classloader: sun.misc.Launcher$AppClassLoader@11b86e7 and when it fails, this is logged 2008-10-24 16:33:04,343 INFO [org.jbpm.jpdl.par.ResourceAction] context classloader: org.jbpm.instantiation.ProcessClassLoader@cbc0bc 2008-10-24 16:33:04,343 INFO [org.jbpm.jpdl.par.ResourceAction] parent of context classloader: sun.misc.Launcher$AppClassLoader@11b86e7 2008-10-24 16:33:04,343 INFO [org.jbpm.jpdl.par.ResourceAction] class classloader: sun.misc.Launcher$AppClassLoader@11b86e7 2008-10-24 16:33:04,343 INFO [org.jbpm.jpdl.par.ResourceAction] parent of class classloader: sun.misc.Launcher$ExtClassLoader@35ce36 So somehow if MVN picks up jdk 6 from the JAVA_HOME, then the classloaders change.. tomorrow i investigate further > 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] Created: (JBPM-1720) JcrDbTest

by Thomas Diesler (JIRA)

JcrDbTest --------- Key: JBPM-1720 URL: https://jira.jboss.org/jira/browse/JBPM-1720 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.HibernateException: instance not of expected entity type: org.jbpm.context.exe.variableinstance.JcrNodeInstance is not a: org.jbpm.context.exe.VariableInstance at org.hibernate.persister.entity.AbstractEntityPersister.getSubclassEntityPersister(AbstractEntityPersister.java:3640) at org.hibernate.impl.SessionImpl.getEntityPersister(SessionImpl.java:1347) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:180) -- 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
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues October 2008