[JBoss JIRA] Created: (JBPM-2566) GWT Console throws exception when trying to "View Deployments"
by George Atala (JIRA)
GWT Console throws exception when trying to "View Deployments"
--------------------------------------------------------------
Key: JBPM-2566
URL: https://jira.jboss.org/jira/browse/JBPM-2566
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.1
Environment: JBoss 5.0, JBPM 4.1, Java 1.6, Mac OSX 10.5.8
Reporter: George Atala
Under Runtime / Deployments, click Refresh. The console displays an error window, with the stack trace shown below. However, obtaining a list of deployments programmatically works fine, using: repositoryService.createDeploymentQuery().list();
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
* URL: 'http://localhost:8080/gwt-console-server/rs/engine/deployments'
* Action: 'org.jboss.bpm.console.client.engine.UpdateDeploymentsAction'
* Exception: 'class com.google.gwt.http.client.RequestException'
HTTP 500:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2009-10-05 17:08:30,413 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/gwt-console-server].[Resteasy]] (http-127.0.0.1-8080-3) Servlet.service() for servlet Resteasy threw exception
org.jboss.resteasy.spi.UnhandledException: java.lang.NullPointerException
at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319)
at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230)
at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:637)
Caused by: java.lang.NullPointerException
at org.jbpm.integration.console.ModelAdaptor.adoptDeployment(ModelAdaptor.java:198)
at org.jbpm.integration.console.ProcessEnginePluginImpl.getDeployments(ProcessEnginePluginImpl.java:54)
at org.jboss.bpm.console.server.EngineFacade.getDeployments(EngineFacade.java:75)
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:597)
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117)
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166)
at org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
... 28 more
--
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
14 years, 5 months
[JBoss JIRA] Created: (JBPM-2711) Subprocess waiting at <state> throws JbpmException 'is not active: inactive-scope' even though isActive() returns true and findActiveActivityNames() returns the correct active state activity (4.2 & 4.3 exhibit same error).
by Martin Porter (JIRA)
Subprocess waiting at <state> throws JbpmException 'is not active: inactive-scope' even though isActive() returns true and findActiveActivityNames() returns the correct active state activity (4.2 & 4.3 exhibit same error).
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBPM-2711
URL: https://jira.jboss.org/jira/browse/JBPM-2711
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Eclipse 3.5, Oracle 11g, jBPM 4.3 & jBPM 4.2
Reporter: Martin Porter
I have a sub-process that is waiting at a <state> activity. If I attempt to signal that activity using the subprocess id I get an exception with 'inactive scope'. Below is the code I am using to signal the activity and also the output (system.out) to show the status:-
ProcessInstanceQuery query = executionService.createProcessInstanceQuery().processDefinitionId(childProcessDefinition.getId());
ProcessInstance childInstance = query.uniqueResult();
System.out.println("Found Child Process Instance With Id [" + childInstance.getId() + "]");
System.out.println("Is Active ? " + childInstance.isActive(BUSINESS_SERVICE_RESPONSE_HANDLER));
System.out.println("State = " + childInstance.getState());
Set<String> activities = childInstance.findActiveActivityNames();
for (String activity : activities) {
System.out.println("Active Activity = " + activity);
}
executionService.signalExecutionById(childInstance.getId(), AbstractServiceDispatcher.SignalState.SUCCESS.getSignalName(), params);
And here follows the output & stack trace:-
Is Active ? true
State = inactive-scope
Active Activity = Business Service Response Handler
11:25:30,862 FIN | [ExecuteActivity] execution[org.jbpm.examples.subprocess.usecase.waitstate.child.30020.Business Service Response Handler] executes activity(Business Service Response Handler)
11:25:30,862 FIN | [ExecuteJobCmd] executed job ExecuteActivityMessage[30054]
11:25:30,862 FIN | [HibernateSessionResource] ----- committing hibernate tx 10796546 -------------------------------------------------------
11:25:32,828 FIN | [HibernateSessionResource] ----- beginning hibernate tx 11998234 --------------------------------------------------------
11:25:32,828 FIN | [HibernateSessionResource] ----- committing hibernate tx 32888473 -------------------------------------------------------
11:25:32,828 FIN | [HibernateSessionResource] ----- beginning hibernate tx 21290107 --------------------------------------------------------
11:25:32,829 FIN | [HibernateSessionResource] ----- committing hibernate tx 22589165 -------------------------------------------------------
Found Child Process Instance With Id [org.jbpm.examples.subprocess.usecase.waitstate.child.30020]
11:25:32,829 FIN | [HibernateSessionResource] ----- beginning hibernate tx 23590079 --------------------------------------------------------
### EXCEPTION ###########################################
11:25:32,829 INF | [DefaultCommandService] exception while executing command org.jbpm.pvm.internal.cmd.SignalCmd@88e83d
org.jbpm.api.JbpmException: execution[org.jbpm.examples.subprocess.usecase.waitstate.child.30020] is not active: inactive-scope
at org.jbpm.pvm.internal.model.ExecutionImpl.checkActive(ExecutionImpl.java:1024)
at org.jbpm.pvm.internal.model.ExecutionImpl.signal(ExecutionImpl.java:411)
at org.jbpm.pvm.internal.cmd.SignalCmd.execute(SignalCmd.java:61)
at org.jbpm.pvm.internal.cmd.SignalCmd.execute(SignalCmd.java:35)
at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43)
at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.signalExecutionById(ExecutionServiceImpl.java:92)
at org.jbpm.examples.subprocess.usecase.waitstate.SimpleSubflowUsecaseWaitStateTest.testSimpleSubflowRequestRetryThenSkipStepThenEndSuccess(SimpleSubflowUsecaseWaitStateTest.java:700)
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:597)
at junit.framework.TestCase.runTest(TestCase.java:164)
at org.jbpm.test.BaseJbpmTestCase.runTest(BaseJbpmTestCase.java:80)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
### EXCEPTION ###########################################
11:25:32,829 FIN | [HibernateSessionResource] ----- rolling back hibernate tx 4657294 -----------------------------------------------------
11:25:32,829 SEV | [BaseJbpmTestCase]
### EXCEPTION ###########################################
11:25:32,829 SEV | [BaseJbpmTestCase] TEST THROWS EXCEPTION: execution[org.jbpm.examples.subprocess.usecase.waitstate.child.30020] is not active: inactive-scope
org.jbpm.api.JbpmException: execution[org.jbpm.examples.subprocess.usecase.waitstate.child.30020] is not active: inactive-scope
at org.jbpm.pvm.internal.model.ExecutionImpl.checkActive(ExecutionImpl.java:1024)
at org.jbpm.pvm.internal.model.ExecutionImpl.signal(ExecutionImpl.java:411)
at org.jbpm.pvm.internal.cmd.SignalCmd.execute(SignalCmd.java:61)
at org.jbpm.pvm.internal.cmd.SignalCmd.execute(SignalCmd.java:35)
at org.jbpm.pvm.internal.svc.DefaultCommandService.execute(DefaultCommandService.java:42)
at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:54)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.execute(EnvironmentInterceptor.java:40)
at org.jbpm.pvm.internal.svc.RetryInterceptor.execute(RetryInterceptor.java:55)
at org.jbpm.pvm.internal.svc.SkipInterceptor.execute(SkipInterceptor.java:43)
at org.jbpm.pvm.internal.svc.ExecutionServiceImpl.signalExecutionById(ExecutionServiceImpl.java:92)
at org.jbpm.examples.subprocess.usecase.waitstate.SimpleSubflowUsecaseWaitStateTest.testSimpleSubflowRequestRetryThenSkipStepThenEndSuccess(SimpleSubflowUsecaseWaitStateTest.java:700)
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:597)
at junit.framework.TestCase.runTest(TestCase.java:164)
at org.jbpm.test.BaseJbpmTestCase.runTest(BaseJbpmTestCase.java:80)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
### EXCEPTION ###########################################
11:25:32,829 SEV | [BaseJbpmTestCase]
--
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
14 years, 5 months
Jbpm4.3+Grails 1.2--- Meet the error : Invalid property 'dbid' of bean class [org.jbpm.pvm.internal.repository.DeploymentProperty]
by weihong
dear:
When I use jbpm 4.3 and grails 1.2 to deploy my process file, I met the following error:
Caused by: org.codehaus.groovy.runtime.InvokerInvocationException: org.springframework.beans.NotReadablePropertyException: Invalid property 'dbid' of bean class [org.jbpm.pvm.internal.repository.DeploymentProperty]: Bean property 'dbid' is not readable or has an invalid getter method: Does the return type of the getter match the parameter type of the setter?
My configuration is as follows:
hibernate.cfg.xml
<hibernate-configuration>
<session-factory>
<mapping resource="jbpm.repository.hbm.xml" />
<mapping resource="jbpm.execution.hbm.xml" />
<mapping resource="jbpm.history.hbm.xml" />
<mapping resource="jbpm.task.hbm.xml" />
<mapping resource="jbpm.identity.hbm.xml" />
</session-factory>
</hibernate-configuration>
spring/resources.groovy
beans = {
springHelper(org.jbpm.pvm.internal.processengine.SpringHelper) {
jbpmCfg = "jbpm.cfg.xml"
}
processEngine(springHelper:"createProcessEngine")
}
jbpm.cfg.xml
<jbpm-configuration>
<import resource="jbpm.default.cfg.xml" />
<import resource="jbpm.tx.spring.cfg.xml" />
<import resource="jbpm.jpdl.cfg.xml" />
<import resource="jbpm.bpmn.cfg.xml" />
<import resource="jbpm.identity.cfg.xml" />
<import resource="jbpm.businesscalendar.cfg.xml" />
<import resource="jbpm.console.cfg.xml" />
<import resource="jbpm.jobexecutor.cfg.xml" />
</jbpm-configuration>
deploy code：
def processEngine
def init = { servletContext ->
def repositoryService=processEngine.getRepositoryService()
def deploymentId = repositoryService.createDeployment()
.addResourceFromClasspath("jbpm/processes/start2end.jpdl.xml")
.deploy(); // the error happen
}
According the error message,I find the org.jbpm.pvm.internal.repository.DeploymentProperty ,and add the following code:
public long getDbid(){
return dbid;
}
and recompiled the jbpm source code, the error disappear!!
I think this maybe a bug of Jbpm 4.3!Do you think so?
And there is another question,if in my spring/resources.groovy, I config the jBPM services such as repositoryService,executionService, the configuratioin is as follows:
beans = {
springHelper(org.jbpm.pvm.internal.processengine.SpringHelper) {
jbpmCfg = "jbpm.cfg.xml"
}
processEngine(springHelper:"createProcessEngine")
repositoryService(processEngine:"getRepositoryService") //error happen
}
the error is as follows:
2010-01-11 15:42:31,140 [main] ERROR context.ContextLoader - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'repositoryService': Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.jbpm.api.RepositoryService org.jbpm.pvm.internal.processengine.ProcessEngineImpl.getRepositoryService()] threw exception; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'repositoryService': Requested bean is currently in creation: Is there an unresolvable circular reference?
at org.grails.tomcat.TomcatServer.start(TomcatServer.groovy:135)
at grails.web.container.EmbeddableServer$start.call(Unknown Source)
at _GrailsRun_groovy$_run_closure5_closure12.doCall(_GrailsRun_groovy:158).....
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.jbpm.api.RepositoryService org.jbpm.pvm.internal.processengine.ProcessEngineImpl.getRepositoryService()] threw exception; nested exception is org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'repositoryService': Requested bean is currently in creation: Is there an unresolvable circular reference?
... 23 more
Caused by: org.springframework.beans.factory.BeanCurrentlyInCreationException: Error creating bean with name 'repositoryService': Requested bean is currently in creation: Is there an unresolvable circular reference?
at org.jbpm.pvm.internal.processengine.SpringProcessEngine.get(SpringProcessEngine.java:109)
at org.jbpm.pvm.internal.processengine.ProcessEngineImpl.getRepositoryService(ProcessEngineImpl.java:172)
... 23 more
I can't find the resolve solution of this error, so I only use the code such as def repositoryService=processEngine.getRepositoryService() to get the jbpm services.Do you have some advice?
14 years, 5 months
[JBoss JIRA] Created: (JBPM-2712) Ability to add timer to transitions in <custom> activity in the same way that they can be added to the <state> task.
by Martin Porter (JIRA)
Ability to add timer to transitions in <custom> activity in the same way that they can be added to the <state> task.
--------------------------------------------------------------------------------------------------------------------
Key: JBPM-2712
URL: https://jira.jboss.org/jira/browse/JBPM-2712
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Reporter: Martin Porter
It should be possible to add a <timer> as the child of the <transition> element contained within a <custom> activity in the same manner that it is for <state> activities. If a custom activity executes a waitForSignal() inside the execute() element (as is the case in our use case) then we need to be able to put a timeout on this activity such that if no signal is recieved within a specified period the timeout will fire and action can be taken. This is possible in a <state> activity but currently not in the custom activity. We tried to do this by changing our <custom> with a <state> and this worked for the timeout but the signalling then failed (see JIRA JBPM-2711) so currenty we can find no solution to this issue.
--
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
14 years, 5 months
[JBoss JIRA] Created: (JBPM-2709) Ant installer fails on start.eclipse with osx (mac) eclipse install
by Eric D. Schabell (JIRA)
Ant installer fails on start.eclipse with osx (mac) eclipse install
-------------------------------------------------------------------
Key: JBPM-2709
URL: https://jira.jboss.org/jira/browse/JBPM-2709
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.x
Environment: osX 10.4.11, intel x86, macbook
Reporter: Eric D. Schabell
Priority: Minor
Fix For: jBPM 4.x
Attachments: build.xml.diff
In jbpm-4.3/install, 'ant start.eclipse' fails with message:
Buildfile: build.xml
[echo] database......... hsqldb
[echo] tx............... standalone
[echo] mail.smtp.host... localhost
start.eclipse:
[exec] -data: line 1: ../../jbpm-4.3/eclipse/eclipse: No such file or directory
[exec] Result: 127
BUILD SUCCESSFUL
Total time: 1 second
Seems like you have two options:
1) provide a symlink to the correct location: ln -s PATH_TO_INSTALL/jbpm-4.3/ecipse/Eclipse.app/Contents/MacOS/eclipse PATH_TO_INSTALL/jbpm-4.3/eclipse/eclipse
2) start eclipse using correct path: ../../jbpm-4.3/ecipse/Eclipse.app/Contents/MacOS/eclipse
I prefer the second so you need to update the jbpm-4.3/install/build.xml script as follows:
--- build.xml 2009-12-28 11:10:36.000000000 +0100
+++ fixed-build.xml 2009-12-30 15:31:20.000000000 +0100
@@ -759,7 +759,7 @@
</fileset>
</chmod>
<exec executable="/bin/bash" os="Linux,Mac OS X">
- <arg line="-c "${jbpm.home}/eclipse/eclipse" "-data" "${jbpm.home}/workspace"" />
+ <arg line="-c "${jbpm.home}/eclipse/jbpm-4.3/ecipse/Eclipse.app/Contents/MacOS/eclipse" "-data" "${jbpm.home}/workspace"" />
</exec>
</target>
Will attach this diff file for you.
--
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
14 years, 5 months
[JBoss JIRA] Created: (JBPM-2679) ExecutionService deleteProcessInstance() and deleteProcessInstanceCascade() silently fails if processinstance is not found
by Peter Horvath (JIRA)
ExecutionService deleteProcessInstance() and deleteProcessInstanceCascade() silently fails if processinstance is not found
--------------------------------------------------------------------------------------------------------------------------
Key: JBPM-2679
URL: https://jira.jboss.org/jira/browse/JBPM-2679
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.x
Environment: JBPM 4.2
Reporter: Peter Horvath
ExecutionService deleteProcessInstance() and deleteProcessInstanceCascade() should throw an exception if the specified process instance is not found.
Current ExecutionService deleteProcessInstance() and deleteProcessInstanceCascade() implementations call the method public void deleteProcessInstance(String processInstanceId, boolean deleteHistory) in DbSessionImpl
The code tries to lookup the process instance, but the deletion is only attempted if the process instance is found:
ExecutionImpl processInstance = (ExecutionImpl) findProcessInstanceByIdIgnoreSuspended(processInstanceId);
if (processInstance!=null) {
// delete remaining tasks for this process instance
List<TaskImpl> tasks = findTasks(processInstanceId);
for (TaskImpl task: tasks) {
session.delete(task);
}
// delete remaining jobs for this process instance
JobImpl currentJob = EnvironmentImpl.getFromCurrent(JobImpl.class, false);
List<JobImpl> jobs = findJobs(processInstanceId);
for (JobImpl job: jobs) {
if (job!=currentJob){
session.delete(job);
}
}
if (log.isDebugEnabled()) {
log.debug("deleting process instance "+processInstanceId);
}
session.delete(processInstance);
}
Since not finding a process instance usually indicates an error, the method should throw an exception to notify caller code.
I think this code should be modified to throw an exception if the process instance is not found:
ExecutionImpl processInstance = (ExecutionImpl) findProcessInstanceByIdIgnoreSuspended(processInstanceId);
if (processInstance==null) {
throw new JbpmException("processInstance is not found");
}
...
--
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
14 years, 5 months
[JBoss JIRA] Created: (JBPM-2716) Protected org.jbpm.pvm.internal.processengine.createProcessEngine() causes validation errors in spring
by Florent Legendre (JIRA)
Protected org.jbpm.pvm.internal.processengine.createProcessEngine() causes validation errors in spring
------------------------------------------------------------------------------------------------------
Key: JBPM-2716
URL: https://jira.jboss.org/jira/browse/JBPM-2716
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.3
Environment: spring 2.5, java 1.6
Reporter: Florent Legendre
Priority: Minor
The new way (4.3) of configuring the ProcessEngine as a bean is as far as I understood through a SpringHelper:
<bean id="jbpmConfiguration"
class="org.jbpm.pvm.internal.processengine.SpringHelper">
<property name="jbpmCfg" value="jbpm.spring.cfg.xml"/>
</bean>
<bean id="processEngine"
factory-bean="jbpmConfiguration"
factory-method="createProcessEngine" />
This works (I have access to the processEngine) but without side effect: spring factory-methods are supposed to be public, and my IDE issues warnings. Can't this method be set public?
--
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
14 years, 5 months