June 2008 - jbpm-issues - Jboss List Archives

[JBoss JIRA] Resolved: (JBPM-164) process domain object update logs

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-164?page=all ] Thomas Diesler resolved JBPM-164. --------------------------------- Resolution: Out of Date > process domain object update logs > --------------------------------- > > Key: JBPM-164 > URL: http://jira.jboss.com/jira/browse/JBPM-164 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Optional > > we could add support for logging updates to process domain objects. > we maintain the logs for all the values that are stored in the process variables. but we cannot store logs for changes that are done in referenced objects. > it would be nice to have a mechanism that users can implement an interface to have support for logging updates to their own objects in the process logs. -- 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] Resolved: (JBPM-76) synchronization between concurrent paths of execution

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-76?page=all ] Thomas Diesler resolved JBPM-76. -------------------------------- Resolution: Out of Date > synchronization between concurrent paths of execution > ----------------------------------------------------- > > Key: JBPM-76 > URL: http://jira.jboss.com/jira/browse/JBPM-76 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Minor > > replace milestone with something more generic. -- 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] Resolved: (JBPM-139) Unable to apply aop interceptors to Node

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-139?page=all ] Thomas Diesler resolved JBPM-139. --------------------------------- Resolution: Out of Date > Unable to apply aop interceptors to Node > ---------------------------------------- > > Key: JBPM-139 > URL: http://jira.jboss.com/jira/browse/JBPM-139 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 alpha 4 > Environment: JBoss 4.0.1 sp1, jboss-aop-1.1.1, (jboss-aop-jdk50.deployer), jdk1.5.0_02, Win XP sp2 > Reporter: David Good > Assigned To: Tom Baeyens > Priority: Minor > > When attempting to apply any interceptor to org.jbpm.graph.Node the exception below is reported. The result is the same for all subclasses of Node. > This is a major problem for predictive scheduling. > java.lang.RuntimeException: failed to transform: org.jbpm.graph.def.Node > at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:626) > at org.jboss.aop.AspectManager.translate(AspectManager.java:572) > at org.jboss.aop.AspectManager.transform(AspectManager.java:490) > at org.jboss.aop.standalone.AOPTransformer.aspectTransform(AOPTransformer.java:59) > at org.jboss.aop.standalone.AOPTransformer.transform(AOPTransformer.java:51) > at sun.instrument.TransformerManager.transform(TransformerManager.java:122) > at sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:155) > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:620) > at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) > at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) > at java.net.URLClassLoader.access$100(URLClassLoader.java:56) > at java.net.URLClassLoader$1.run(URLClassLoader.java:195) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:188) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) > at java.lang.ClassLoader.loadClass(ClassLoader.java:251) > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) > at org.jbpm.jpdl.par.ProcessArchive.createProcessDefinition(ProcessArchive.java:92) > at com.axxia.workflow.afcl.service.AbstractProcessTest.deployArchive(AbstractProcessTest.java:67) > at com.axxia.workflow.afcl.service.TestProcessService.<init>(TestProcessService.java:47) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) > at java.lang.reflect.Constructor.newInstance(Constructor.java:494) > at junit.framework.TestSuite.createTest(TestSuite.java:135) > at junit.framework.TestSuite.addTestMethod(TestSuite.java:114) > at junit.framework.TestSuite.<init>(TestSuite.java:75) > at junit.framework.TestSuite.addTestSuite(TestSuite.java:101) > at com.axxia.workflow.afcl.service.AllTests.suite(AllTests.java:26) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.getTest(RemoteTestRunner.java:401) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:441) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:342) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:194) > Caused by: javassist.CannotCompileException: [source error] sorry, synchronized is not supported > at javassist.CtNewMethod.make(CtNewMethod.java:78) > at javassist.CtNewMethod.make(CtNewMethod.java:44) > at org.jboss.aop.instrument.Instrumentor.addBaseElements(Instrumentor.java:642) > at org.jboss.aop.instrument.Instrumentor.setupBasics(Instrumentor.java:875) > at org.jboss.aop.instrument.MethodExecutionTransformer.instrument(MethodExecutionTransformer.java:191) > at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:574) > ... 38 more > Caused by: compile error: sorry, synchronized is not supported > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:346) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:325) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.CodeGen.atMethodBody(CodeGen.java:266) > at javassist.compiler.CodeGen.atMethodDecl(CodeGen.java:248) > at javassist.compiler.ast.MethodDecl.accept(MethodDecl.java:43) > at javassist.compiler.Javac.compileMethod(Javac.java:158) > at javassist.compiler.Javac.compile(Javac.java:93) > at javassist.CtNewMethod.make(CtNewMethod.java:73) -- 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] Resolved: (JBPM-102) optimize performance for delegation instantiation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-102?page=all ] Thomas Diesler resolved JBPM-102. --------------------------------- Resolution: Out of Date > optimize performance for delegation instantiation > ------------------------------------------------- > > Key: JBPM-102 > URL: http://jira.jboss.com/jira/browse/JBPM-102 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Optional > > delegation instantiation could be optimized by object pooling. this might require a configuration property on the delegation xml to specify the scope of a delegation object {new-for-each-usage, synchronized, singleton} > note that ExpressionAssignmentHandler is not threadsafe. -- 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] Resolved: (JBPM-160) User thrown exceptions in ActionHandler logs severe error

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-160?page=all ] Thomas Diesler resolved JBPM-160. --------------------------------- Resolution: Out of Date > User thrown exceptions in ActionHandler logs severe error > --------------------------------------------------------- > > Key: JBPM-160 > URL: http://jira.jboss.com/jira/browse/JBPM-160 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0 alpha 5 > Environment: All > Reporter: Jim Rigsbee > Assigned To: Tom Baeyens > Priority: Minor > Original Estimate: 1 day > Remaining Estimate: 1 day > > Users are intended to throw exceptions from their action handlers in order to end processing that is "undoable". Currently the core logs this as a SEVERE error and dumps a stacktrace. This should be considered "business as usual" and at most logged as INFO. -- 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] Resolved: (JBPM-148) add variable support for BigDecimal

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-148?page=all ] Thomas Diesler resolved JBPM-148. --------------------------------- Resolution: Out of Date > add variable support for BigDecimal > ----------------------------------- > > Key: JBPM-148 > URL: http://jira.jboss.com/jira/browse/JBPM-148 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Optional > -- 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] Resolved: (JBPM-75) make event propagation configurable

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-75?page=all ] Thomas Diesler resolved JBPM-75. -------------------------------- Resolution: Out of Date > make event propagation configurable > ----------------------------------- > > Key: JBPM-75 > URL: http://jira.jboss.com/jira/browse/JBPM-75 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Optional > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > event propagation might become a bottleneck in high-throughput deployments. > the easiest way to solve this is by introducing a configuration property that overrides the default behaviour of event propagation. the current default is that event propagation is active. -- 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] Resolved: (JBPM-55) develop aop strategy for action-events, logging and security

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-55?page=all ] Thomas Diesler resolved JBPM-55. -------------------------------- Resolution: Out of Date > develop aop strategy for action-events, logging and security > ------------------------------------------------------------ > > Key: JBPM-55 > URL: http://jira.jboss.com/jira/browse/JBPM-55 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Minor > -- 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] Resolved: (JBPM-69) add support for method events

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-69?page=all ] Thomas Diesler resolved JBPM-69. -------------------------------- Resolution: Out of Date > add support for method events > ----------------------------- > > Key: JBPM-69 > URL: http://jira.jboss.com/jira/browse/JBPM-69 > Project: JBoss jBPM > Issue Type: Task > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Minor > > for simple method events, users should not be forced to use aop. simple actions e.g. on the before-signal or the after-start event-types should be sufficient. -- 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] Resolved: (JBPM-67) add support for process-local variable-type-determination

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-67?page=all ] Thomas Diesler resolved JBPM-67. -------------------------------- Resolution: Out of Date > add support for process-local variable-type-determination > --------------------------------------------------------- > > Key: JBPM-67 > URL: http://jira.jboss.com/jira/browse/JBPM-67 > Project: JBoss jBPM > Issue Type: Feature Request > Components: Core Engine > Reporter: Tom Baeyens > Assigned To: Tom Baeyens > Priority: Optional > > now, the way that a process variable is persisted, is configured in the jbpm.types.properties. > one set of all types determinations for the whole jbpm installation. > we should allow users to overwrite this mechanism on a process definition level. > in the process definition, the same information can be given for process variable names. > <variable name="myvar" tranformer="" variable-instance="" /> > or > <variable java-type="org.MyType" tranformer="" variable-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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbpm-issues June 2008